List Export Templates

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

Annotations already declare readOnlyHint=true and destructiveHint=false, providing safety guarantees. The description adds minor context about 'quick recurring exports' but does not disclose pagination, sorting, or search behaviors. With annotations present, the description is adequate but adds marginal value.

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?

The description is a single sentence that is front-loaded with the use case. It is concise and contains no wasted words.

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?

Given the tool has 5 parameters, 2 enums, and an output schema, the description lacks details on pagination, filtering, and sorting capabilities. However, since an output schema exists, the return structure is documented elsewhere. The description is incomplete regarding how to effectively use the parameters.

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 100%, so all parameters are fully described in the input schema. The tool description does not add any additional meaning beyond what the schema provides, meeting the baseline.

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 clearly states the tool's purpose: to view saved export templates for recurring exports. It uses a specific verb 'see' (list) and resource 'export templates', and distinguishes from siblings like export_template_get (single) and export_template_create.

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 gives a clear when-to-use ('when the user wants to see their saved export templates'), but does not explicitly mention when not to use it or compare with alternatives like export_template_get for single templates. Context is clear but guidance is incomplete.

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