get_recipe

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

The description implies a read operation, but with no annotations, it does not disclose prerequisites (e.g., recipe must exist) or potential side effects. The phrase 'full details' lacks specific behavioral context beyond retrieval.

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?

A single, front-loaded sentence of 9 words. No superfluous content; every word earns its place.

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 simple read tool with one parameter and an output schema, the description is mostly complete. However, it lacks guidance on usage context (e.g., when to choose this over get_recipe_nutrition) and does not mention error handling.

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?

With 0% schema description coverage, the description adds meaning by specifying that 'slug' is the identifier. This is more informative than the schema alone, but it does not explain format or constraints (e.g., where to find the slug).

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 action (Get), resource (full details of a recipe), and identifier (by slug). This distinguishes it from sibling tools like list_recipes (listing all) and get_recipe_nutrition (nutrition only).

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?

No guidance on when to use this tool versus alternatives such as get_recipe_nutrition or list_recipes. The agent must infer usage from the name alone.

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