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

Annotations already declare readOnlyHint and idempotentHint, so safety is covered structurally; the description adds value beyond that by disclosing the return format (markdown), the instruction to answer from the text and cite its URL rather than rely on memory, and the exact-URL requirement. It does not discuss pagination or truncation of long guides, a minor residual gap for a full-text fetch.

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?

Front-loads the action and output format, then the trigger, then the sibling disambiguation. Every clause carries distinct information — no filler, no repetition of the title or schema.

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?

No output schema exists, so the description carries the return-value burden and does so ('as markdown'), along with sourcing expectations and the URL-passing rule. For a one-parameter read tool with safety annotations, nothing an agent needs to call it correctly is missing.

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%, so the baseline would be 3, but the description adds real guidance beyond the schema: the URL must be passed exactly as search_recipes returned it, and it reinforces the absolute-URL requirement. That is meaningful behavioral constraint on the single parameter, not just restatement.

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 the full text of a cooking guide from recipes-daily.com, as markdown') and explicitly separates itself from the sibling show_recipes by defining what a guide is versus a recipe. An agent can route between read_guide and show_recipes without opening either schema.

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?

Gives an explicit trigger ('Call this when search_recipes lists a guide that answers the question'), enumerates the question types guides cover (how/why, storage, substitution, equipment), and names the alternative for the excluded case ('For recipes, use show_recipes instead'). Both the when and the when-not are present.

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