subscription_templates_list

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safe-read profile is covered structurally. The description adds genuinely useful behavior beyond the annotations: it returns templates without their content payload. It still omits ordering/pagination details, so it lands at an adequate 3.

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 short phrase, effectively front-loaded with no wasted words. The only blemish is the typo 'wihout', otherwise near-ideal conciseness for a simple list tool.

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 no-parameter list tool with annotations covering safety and no output schema, the description supplies the one non-obvious fact (content is excluded). Nothing critical is missing, though it could note ordering or empty-result behavior.

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 has zero parameters, so there is nothing to document and the schema/semantics burden is nil. Baseline 4 applies; the description adds no parameter detail because none is needed.

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 (Get/list) and resource (subscription templates), which distinguishes it from the singular sibling subscription_templates_get. The '(without content)' scoping note further clarifies what is returned, though the misspelling 'wihout' and lack of explicit contrast with sibling list/get tools keep it from a 5.

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 explicit when-to-use guidance or alternatives are named. An agent must infer from the name alone that this lists all templates versus subscription_templates_get for a single one. The 'without content' hint is the only usage-adjacent signal.

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