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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds real behavioural context beyond that: cardinality (one illustration per guide/comparison/diagnosis etc.) and the fact that glossary, methods, policies, standards and tools share a single plate rather than having per-page art. It stops short of saying what happens when a page has no illustration assigned.

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?

Two sentences, front-loaded with the return payload before the per-family cardinality rule; no filler. The compressed phrases 'shared plate' and 'solve-backwards question' cost a little clarity for the token saving but stay readable.

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 a full output schema and 100%-covered input schema, the description carries little structural burden, and it still supplies the family/cardinality rule an agent needs to pick parameters correctly. Only the empty-result case is unaddressed, which is a minor gap for this complexity.

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 genuine meaning: it maps the family enum values to their cardinality, explaining that the shared-plate families return the same drawing regardless of slug. That clarifies the interaction between the two parameters in a way 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?

The first clause names a specific verb and resource — 'Returns the topic illustration a page of the site carries' — and enumerates the payload (SVG address, subject, licence). It is distinguishable from mutation siblings like create_drawing or export_drawing, though it never names the read/retrieval alternatives (fetch, open_in_site_link) it sits beside.

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 only implied: 'the topic illustration a page ... carries' suggests calling it when you need the artwork for a given page. There is no explicit when-to-use, when-not-to-use, or reference to a sibling for the same need, so the agent must infer the selection rule.

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