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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds value beyond that by disclosing the return content shape - template categories plus 'the fields each one needs' - which is the key behavioral fact for a listing tool. No pagination or rate-limit behavior is mentioned, but a static template catalogue plausibly has none.

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, front-loaded with the resource and its coverage, then the routing instruction. No filler, and every clause earns its place.

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 one-parameter read-only listing tool with no output schema, the description covers purpose, content, and the natural follow-up tool, which is nearly everything an agent needs. Minor gaps remain: it does not describe the returned structure beyond field lists, nor note that locale changes the returned labels/links.

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 100% and the 'locale' parameter is fully documented in the schema with its enum and default. The description says nothing about locale, so it adds no meaning beyond the schema; baseline 3 applies.

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 ready-made transaction manifest templates') and enumerates the concrete template categories covered (transfer, stake, mint, burn, faucet...). It distinguishes itself from the many build_* siblings by naming build_manifest_from_template as the renderer, so an agent can tell this is the discovery/listing tool.

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: 'Use build_manifest_from_template to render one,' which is a clear follow-up condition and separates this tool from all the build_* siblings. It does not state any when-not condition (e.g., that this is static and needs no prior setup), so it falls short of a full 5.

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