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

Annotations already cover read-only, idempotent, non-destructive safety, so the description correctly focuses on what they cannot express: the 6-item cap, the tighter 3-item cap for recipe depth, and that unavailable/private scenes collapse to a generic error. The generic-error disclosure is genuinely useful because it warns the agent it cannot distinguish 'not found' from 'forbidden'.

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?

Three sentences, none wasted, with the primary action and scope front-loaded before the batch limits and the error-behavior caveat.

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?

An output schema exists so return values need not be described, and the safety profile is annotated. The remaining gap is the unexplained depth enum, but for a two-parameter read tool the definition is otherwise complete enough to call 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 0%, so the description must carry the load. It partially does by restating the six-item ceiling and tying 'recipe batches' to the depth enum's recipe value, but the card/sheet/recipe depth levels and their effect on output are never explained, leaving the only meaningful parameter semantics to guesswork.

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 (read) and resource (scene references) plus the batch-and-compare semantics, which separates it from the singular get_scene sibling by implication. It never names the sibling outright, so differentiation requires a small inference.

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?

'for comparison' and 'Recipe batches are limited to three' imply the multi-scene comparison use case and one hard constraint, but there is no explicit when-to-use vs get_scene / search_scenes guidance or statement of when a single fetch is preferable.

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