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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety and scope are covered elsewhere. The description adds only the vague phrase 'with their fields', giving no insight into result size, ordering, pagination, or whether deleted/archived templates are included.

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?

Very short with no wasted clauses, but it is an incomplete sentence fragment rather than a front-loaded verb-object statement. Brevity here reflects under-specification rather than disciplined editing.

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, read-only list tool with no output schema, the bar is low, and 'with their fields' partially signals that full template objects are returned. Still missing: whether all templates are returned or a page, and how it relates to get_template/save_template/delete_template in the template lifecycle.

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 and the schema is fully specified, so there is no parameter semantics to explain; baseline of 4 applies. The description correctly avoids inventing filter parameters that do not exist.

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 names the resource ('saved push templates') and hints at return contents ('with their fields'), but it is a noun phrase with no verb, so the agent must infer that this lists templates rather than e.g. counts or validates them. Siblings like get_template and list_pushes make the intent guessable, but the description never differentiates itself from them explicitly.

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?

No guidance on when to use this vs get_template (single template) or list_pushes; nothing indicates whether results are paginated, filtered, or complete. The agent must infer list semantics purely from the plural resource noun.

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