get_recipe

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

Lists all return fields (name, author, time, etc.) and notes id format. No annotations, but description adequately discloses output contents. Lacks mention of error handling or authentication.

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?

Concise, front-loaded main sentence, uses structured Args section. No unnecessary words.

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?

Single parameter, output schema exists, siblings cover other actions. Description covers what, how, and what is returned completely.

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 has only title and type for recipe_id; description adds example ('1019049') and source ('from a search result or URL'), fully compensating for 0% schema coverage.

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?

Clearly states 'Fetch full details for a single NYT Cooking recipe by its numeric id', with specific verb and resource. Distinguishes from sibling search_recipes which likely returns list.

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?

Implies usage after obtaining a recipe_id from search or URL. Mentions the id origin. Could be more explicit about when not to use, but sufficient for context.

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