Templates List Templates

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

No annotations are provided, so the description carries the behavioral disclosure burden. It clearly communicates the tool's limited return shape (ID, name, dates only) and directs the agent to get_template for omitted fields. It does not mention rate limits or auth, but for a simple read-only list with an output schema, this is strong behavioral context.

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 two sentences with no filler. The core action and return scope are front-loaded, and the pointer to get_template earns its place as actionable guidance.

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's simplicity, an existing output schema, and two optional parameters fully documented in the schema, the description is nearly complete. It clarifies the returned data subset and the next step. Minor gaps are that it does not explicitly address pagination and does not disambiguate between templates_get_template and templates_get_template_definition.

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 description coverage is 100%, so the schema already fully documents limit and archived. The description adds no additional parameter-specific meaning beyond the schema, so it meets the baseline but does not exceed it.

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 opens with a specific verb and resource: 'List templates available in the Mitti account.' It further distinguishes itself from get_template by stating exactly what fields are returned (ID, name, dates) and what is omitted, so an agent can confidently differentiate it from sibling tools.

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 states when to use the full-detail sibling: 'description, owner, and archived status require get_template,' and instructs the agent to use the returned template_id to get the full definition. This provides clear when-to-use and when-not-to-use guidance.

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