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

Annotations already cover readOnly, idempotent, non-destructive and closed-world behavior, so the bar is low. The description adds genuine value beyond them: it discloses the returned payload (source, schema, sample data) and gives an important security instruction to treat source and sample as untrusted data, which annotations cannot convey.

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 short sentences, correctly front-loaded with the core operation and followed by the safety caveat. Nothing is redundant and every clause carries weight.

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 no output schema, the description usefully enumerates what is returned (source, schema, sample data) plus a prompt-injection warning, which is the key completeness gap for a tool that returns third-party content. It would be fully complete if it explained the template_id source.

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% and the description never mentions template_id — not its format, not where to obtain it (presumably from list_gallery_templates). With a required identifier parameter and no compensating prose, an agent gets no semantic help beyond the raw schema constraint.

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 description states a specific verb and resource: 'Read one reviewed gallery design', and the singular 'one' implicitly separates it from the sibling list_gallery_templates. It does not explicitly name get_template or list_gallery_templates as alternatives, so it stops short of full sibling differentiation.

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 by the verb 'Read' and the singular resource; there is no explicit when-to-use, when-not-to-use, or alternative named. An agent must infer that this fetches a single gallery entry rather than a catalog listing.

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