List Templates

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

No annotations are provided, so the description bears full responsibility. It thoroughly explains the behavioral distinction between team templates (usable) and system templates (discovery-only), and what to do when no template matches. No contradictions.

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 sentences, each earning its place: first states purpose, second gives primary usage rule, third covers edge cases. Concise and front-loaded without redundancy.

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 two optional parameters and an output schema (not shown but present), the description covers all relevant scenarios: listing templates, using team vs system, and handling missing templates. No gaps for effective use.

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%, baseline 3. The description adds value for 'include_system' by clarifying that system templates are not directly usable, which the schema's description ('Include discovery-only system templates...') also hints at, but the tool description provides richer context.

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 'List extraction templates for choosing an extraction template,' specifying the verb 'list' and resource 'extraction templates.' It distinguishes from sibling tools like 'extract_file' and 'extract_folder,' which are extraction 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?

The description explicitly instructs agents to use 'team_templates' for processing and explains when to use system templates (discovery-only). It also provides clear guidance for cases with no matching template: ask the user to add a system template or create a custom schema.

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