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

Annotations already declare readOnly/idempotent/non-destructive, so the bar is lower. The description adds real value by disclosing the return shape (summaries, not payloads) and pointing to the tool that returns the payload, though it says nothing about pagination behavior beyond the schema's offset/limit.

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 tight sentences with zero filler; the resource definition comes first and the sibling routing is front-loaded in the second clause.

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?

For a read-only, zero-required-parameter list tool with no output schema, the description covers what it returns (summaries) and where to go for full payloads. Filter semantics rest on the schema, which is acceptable but leaves minor gaps.

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 60%, so the schema carries most parameter meaning. The description's enumeration of media kinds ('images, video, music and motion') loosely maps to the media_kind enum but omits 'voice' and never mentions query, category, limit or offset, so it adds only marginal detail.

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 (browse the public template library) with an explicit definition of what a template is ('curated model + prompt + settings recipes'). It also distinguishes itself from the sibling get_template by stating it returns summaries.

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?

Explicitly routes the agent to get_template when a full ready-to-run payload is needed rather than a summary. Clear use context, but no explicit when-not conditions and no guidance on combining query/category/media_kind filters.

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