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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is well covered. The description adds a useful statement about returning scaled ingredients and steps, which clarifies what the operation yields. No contradiction exists between description and annotations.

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 one focused sentence that says exactly what the tool does and what it returns. It is front-loaded with the main purpose and includes no filler or repetition. Every part 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?

This is a simple, single-parameter read-only tool with a rich output schema, so the description does not need much more. The parameter is fully documented in the schema and the purpose/return content is clearly stated. The agent has enough context to select and invoke this tool correctly.

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% and the meal_id parameter is already documented well as 'Meal ID from search_meals (UUID).' The description references the meal concept but adds no significant parameter details beyond the schema. Baseline 3 is appropriate because the schema carries the semantic weight.

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 states a specific verb and resource: 'Get full recipe details for a specific meal.' It also specifies the content that distinguishes this from other tools — 'scaled ingredients and steps.' This clearly separates it from search_meals and get_flyer_deals.

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 implies this is for fetching details for one specific meal rather than searching or browsing. The input schema reinforces the intended flow by requiring a meal_id from search_meals. It could be stronger with an explicit when-not-to-use statement, but the usage context is clear.

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