Two focused tools with reasonable naming and schema structure, but incomplete schema definitions (truncated JSON), vague descriptions, and unclear use cases limit effectiveness. Schema completeness issues are critical - both input definitions appear cut off mid-property, preventing proper validation. Description text lacks specificity about when/why to use these tools in agent workflows.

• Complete and validate JSON schema definitions - ensure all array/object properties are fully specified with type, description, and required status
• Expand descriptions to 50+ characters with agent-centric language: 'Use to create shareable recipe content that drives ingredient purchases' instead of just 'Create a recipe page'
• Add explicit required array to schemas: {"required": ["title"]} at schema root level
• Document image dimension constraints in schema as pattern/minimum properties or in description
• Specify pagination/limits for array fields (e.g., max instructions, max line items) to guide agent behavior
• Add examples field to schema showing minimal valid input for each tool
• Clarify the relationship between these tools - when would an agent use both together vs. independently?