create_recipe_from_html

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

With no annotations, the description carries the burden of behavioral disclosure. It discloses the parsing mechanism (Mealie or schema.org JSON-LD) and the context of use, but does not mention side effects, permissions, reversal, or return values. It provides some context beyond a bare 'create' verb, but not rich behavioral detail.

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 description is concise and well-structured: three sentences that front-load the core action, then provide usage context and parsing details. Every sentence earns its place with no redundancy or fluff.

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 tool with 3 params and no output schema, the description covers the purpose, usage, and parsing method completely. It clearly addresses the sibling alternative and the failure scenario. It doesn't explain return values or errors, but that's not strictly required given the simplicity and schema coverage.

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 100%, so the baseline is 3. The description does not add significant parameter semantics beyond the schema, but it reinforces that 'html' is raw HTML and the schema already documents sourceUrl and includeTags adequately. No extra meaning is needed.

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?

The description clearly states the tool's purpose: 'Create a recipe from raw HTML that you fetched yourself.' It uses a specific verb and resource, and explicitly differentiates this tool from create_recipe_from_url by explaining when to use each. This distinguishes it from the sibling tool effectively.

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?

The description provides explicit usage guidance: 'Use this when create_recipe_from_url fails because the MCP server can't reach the site.' It even describes the workflow (fetch HTML yourself, pass it here) and the alternative, making it clear when to use this tool versus the sibling.

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