subscription_template_get_all_templates

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

The HTTP GET prefix implies a read-only, non-destructive operation, and '(without content)' discloses that full template bodies are omitted. With no annotations, the description still omits auth requirements, pagination behavior, and potential rate limits, leaving meaningful gaps.

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 and front-loaded, with the key operation stated first. The redundant HTTP endpoint line and 'Tags:' metadata are minor noise, and the typo 'wihout' slightly harms polish but not clarity.

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?

No output schema exists, so the description must carry more burden. It says results exclude content, but does not describe the returned template fields, pagination, or ordering, which an agent may need for correct follow-up calls.

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 parameter semantics carry no burden. Baseline score of 4 is appropriate as there is nothing for the description to clarify beyond the empty schema.

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' and resource 'all subscription templates' with a scope qualifier '(without content)' that distinguishes it from the detail endpoint get_template_by_uuid. However, it does not name alternative sibling tools or further differentiate from related template listing operations.

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 guidance on when to use this tool versus get_template_by_uuid, get_tags, or the mutation tools. The '(without content)' note implies a lightweight listing but does not state conditions or exclusions.

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