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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds only that the call returns file contents for a recipe it runs; it says nothing about what happens when the path is not among the recipe's files or whether content is truncated for large files.

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 with zero filler: verb, resource, concrete examples, and purpose in that order. Nothing is redundant or padded.

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 two-parameter read tool with full schema coverage, an output schema, and annotations covering safety, the description supplies enough to call it correctly. A note on error behavior for invalid paths would make it complete.

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 coverage is 100% and both parameters are documented in the schema, so the baseline is 3. The description's file examples give a sense of what a valid `path` looks like, but it adds no syntax or format detail beyond the schema's 'as the recipe lists it' constraint, and says nothing extra about the `recipe` ID parameter.

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?

States a specific verb and resource ('Read one of a recipe's files') and concretizes it with examples (compose.yaml, Dockerfile, recipe.json) plus the intent ('to see exactly what it runs'). It is clearly distinguishable from search_recipes or get_install, though it never explicitly contrasts with the closest sibling, get_recipe.

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?

Usage is implied by 'to see exactly what it runs', which suggests inspecting file contents rather than recipe metadata. However, no alternative is named and there is no statement of when not to use it, e.g. 'use get_recipe for metadata only'.

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