Single tool 'create_prompt' has a valid schema generated from Zod, but the description is minimal (8 words, well below the 10-char minimum for meaningful context). The schema itself is overly complex and deeply nested, making it difficult for LLMs to understand the expected structure. Parameter descriptions exist but are sparse. The tool performs a write operation (creates a prompt) but the description does not explicitly state this, violating the command-tool pattern. No error recovery guidance is provided. The schema nesting (object → properties → array → items → object → properties) is convoluted and would benefit from simplification or documentation of the expected data shape.

• Expand tool description to 50-150 characters: 'Create a prompt in Ashra by providing a URL, prompt text, and expected data schema. Returns extracted data matching the schema. Requires ASHRA_API_KEY environment variable.'
• Add a 'schema' parameter description explaining the expected structure: 'JSON Schema defining the data to extract. Must be an object with properties (each an array of objects with string fields). Example: {"type": "object", "properties": {"items": {"type": "array", "items": {"type": "object", "properties": {"name": {"type": "string"}}}}}'
• Document the response schema in the tool description: 'Returns {success: boolean, data: {[key]: [{field: value}]}}, a map of property names to arrays of extracted records.'
• Add error handling guidance to the description: 'If the URL is unreachable, the schema is invalid, or the API key is missing, the tool will return an error. Verify the URL is accessible and the schema matches the page structure.'
• Consider splitting the complex 'schema' parameter into a separate discovery tool or simplifying the schema structure to reduce nesting depth and improve clarity.