list_templates

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

With no annotations, the description carries the full behavioral burden. It communicates that this is a listing operation and clarifies the profileName filtering behavior (null=global, name=local, omit=all), which adds value. However, it does not disclose the return format, pagination, sorting, or confirm that calling with no parameters returns all templates.

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?

Three short sentences, each earning its place. The main purpose is front-loaded ('List saved templates'), followed by filter details and the versioned parameter nuance. No wasted words or irrelevant context.

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 simple two-optional-parameter list tool, the description covers the essentials: what it does and how to filter using tag and profileName. It does not explain the return shape, and with no output schema that gap is notable, but the tool's simplicity keeps the description reasonably complete.

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 coverage is only 50% (tag lacks a description). The description compensates by stating 'Optional tag filter,' giving tag its purpose and optionality, and by adding the 'omit=all' behavior for profileName, which goes beyond the schema's 'null = global-only; string = that profile.' This meaningfully helps an agent understand both parameters.

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 and resource: 'List saved templates.' It clearly distinguishes from sibling tools like get_template, delete_template, and execute_template by the list action alone. The optional tag and profileName filters further specify the scope of the operation.

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?

The description implies when to use it by mentioning 'saved templates' and the optional filters, but it never explicitly contrasts it with alternatives like get_template for a single template or save_template for creation. The profileName semantics (global/local/all) give useful context for how to invoke it, but no when-to-use vs. when-not-to-use guidance is present.

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