create_recipe_from_html_or_json

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full behavioral burden. It reveals the method (POST) and that content is "parsed like a URL", but says nothing about authentication requirements, whether duplicates are created, what the response returns, or how parsing failures are handled.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

The substantive content is front-loaded and reasonably tight, but the trailing keyword list is pure SEO padding that repeats the name and adds no decision-relevant information, bloating the definition.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a mutation tool with no annotations, no output schema, and 0% parameter documentation, the description leaves too much unsaid: no return shape, no permissions/auth context, and no explanation of the required nested body object.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate. It only loosely explains the required "data" string (HTML or schema.org JSON) and completely omits the "url", "includeTags", and "includeCategories" fields and the "body" wrapper structure that the schema requires.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("Create recipe") and clarifies the accepted input formats: raw HTML or a schema.org Recipe JSON string. The name itself distinguishes it from the zip/image siblings, but the description never names or contrasts those alternatives explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied through the input-format constraint ("Takes in raw HTML or a https://schema.org/Recipe object as a JSON string"), which implicitly routes agents here rather than to create_recipe_from_zip, create_recipe_from_image, or parse_recipe_url. No explicit when-to-use or exclusion guidance is given.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.