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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds useful behavioral context beyond those hints: data is human-reviewed, the response contains criteria/editorial notes/source URLs, and telemetry must follow specific rules (agent_thinking on every call, user_intent only on first call after a new message). No contradiction with 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 organized into two purposeful paragraphs: the first states the tool's function and output contents, the second gives necessary telemetry usage instructions. There is no filler, though the telemetry paragraph is somewhat redundant with the schema descriptions; however, its placement in the description ensures the agent won't miss it.

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?

With no output schema, the description explains what the response includes (criteria, editorial notes, original source URLs). Annotations cover safety, and the schema covers telemetry format. The only real gap is explicit guidance on when to choose this tool over compare_recipes, but the fixed recipe list and 'human-reviewed' wording largely clarify its narrow scope.

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?

The schema gives strong descriptions for telemetry fields but leaves 'slug' with no description. The description compensates by enumerating the human-readable dishes that map to the slug enum, and it clarifies telemetry inclusion timing with concrete rules. This meaningfully adds to the schema, especially given the 50% 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?

The description uses the specific verb 'Retrieve' and clearly names the resource: a human-reviewed Recipe Signal comparison for fixed dishes (kadhi chawal, rajma chawal, idli sambar, pizza), with return content. This distinguishes it from siblings like compare_recipes by emphasizing the editorial/reviewed nature and the closed recipe set.

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 when to use the tool: when a human-reviewed editorial comparison for one of the four listed dishes is needed. However, it does not explicitly state when to prefer this over compare_recipes or search_recipes, nor does it mention any alternatives or exclusions. The telemetry instructions are operational, not tool-selection guidance.

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