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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered; the description adds real behavioral context beyond that — what the panel entries contain (overlay radius, shadow, backdrop filter, open-motion string, state names) and an edge-case behavior ('Returns available recipe types if the requested one has no matches'). It stops short of stating result size caps or ranking criteria.

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-loaded with purpose then usage then args, and every section is relevant. The middle sentence is dense and runs long, but the detail is substantive rather than padding.

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 must explain the return shape — and it does, describing the ranked panel, per-entry fields, and the no-match fallback. Combined with the full parameter coverage, nothing an agent needs to call this 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 description coverage is 0%, so the description carries the full burden — and it does: recipe_type with five concrete examples, industry as an optional filter with examples, scheme restricted to 'dark'/'light' with its matching semantics, and limit as panel size 1-12 default 8. This supplies meaning the schema does not.

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?

Specific verb+resource ('compare_recipes' returns a ranked cross-product panel) with explicit scope: 'one call, cross-product.' It distinguishes itself from the sibling get_recipe by naming it and stating what each returns, so an agent can pick 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?

Explicit when-to-use ('Use before building any complex pattern') and an explicit alternative with the selecting condition: 'call get_recipe(site, recipe_type) on the one you choose for its full measured anatomy tree.' The when/when-not split is fully specified.

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