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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the discipline is low. The description still adds real behavioral context beyond them: the ordering guarantee ('most recently updated first') and the composition of a template. It stops short of describing return count/pagination.

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?

A single front-loaded sentence leads with verb + resource + ordering, then uses the em-dash tail to define 'template' instead of adding a separate sentence. No redundant or filler text.

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-parameter list tool with no output schema and annotations covering safety, the description is nearly sufficient, and its definition of template contents substitutes for a missing output schema. It could add a note on expected volume/pagination, so not quite perfect.

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?

The tool takes zero parameters, so the schema provides nothing to disambiguate. Per the rubric, a 0-parameter tool earns a baseline of 4; there are no arguments whose meaning could be enriched.

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 (List) and resource (the user's saved post templates) and further defines what a template is (reusable composer states). It clearly distinguishes itself from the singular get_post_template sibling without needing to name it.

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: 'List the user's saved post templates' tells the agent what it does but not when to prefer it over get_post_template or create_post_template. No explicit when-to-use, exclusions, or conditions are given, which is the minimum-viable level.

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