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 usefully adds that entries are templates 'with sample data', but says nothing about result caps, ordering, or what an empty result means, and there is no annotation about result size.

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?

Only two sentences, but the long enumeration of document types (invoices, quotes, receipts, statements ... tickets, labels, menus) consumes most of the budget and largely restates the category enum in the schema. The core distinction — catalog listing versus a single template — is not front-loaded.

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 zero-required-parameter, read-only listing tool with an output schema and annotations, this is close to sufficient: the agent knows what comes back and that it is safe. The remaining gap is how the two filters interact and whether results are paginated or truncated.

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% and both parameters are documented in the schema, so the schema does the heavy lifting. The description's inline examples ('invoice', 'contract') give mild additional intuition for the query string but duplicate the purpose already stated in the schema field description.

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 and resource ('Lists the gallery's ready documents ... each a template with sample data'), so the agent knows this returns template catalog entries rather than document instances. It never names or contrasts with the sibling get_template, so an agent facing both still has to infer which one returns a single template.

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?

The closing sentence ('Search by a word ... or a category') implies the two usage modes but frames them as mechanics rather than when-to-use guidance. There is no statement about when to call get_template instead, or whether both filters can be combined.

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