List figure templates

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

With no annotations, the description fully explains the tool's behavior: it lists templates with slot schemas. It implicitly indicates a read-only, non-destructive operation. However, it could explicitly state that no modifications are made or mention any rate limits, but for a simple list, this is sufficient.

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?

Two sentences contain all essential information without fluff. The first sentence immediately states the action, and the second provides usage guidance. Every word earns its place.

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 that the tool has no parameters and no output schema, the description is fully complete. It tells the agent what the tool does, what it returns (list of templates with slot schemas), and how it should be used (called first). There is no missing context.

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 has zero parameters, so schema coverage is 100% and there is no need for additional parameter semantics. The description does not attempt to add information about non-existent parameters, which is appropriate.

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 identifies the tool's function: lists all diagram templates (16) and the featured cover with their slot schemas. It uses specific verb 'list' and specifies the resource 'diagram templates' and content 'slot schemas'. It distinguishes itself from sibling render tools which have different purposes.

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 tool: 'Call this first to learn what shapes exist and exactly which slots each render tool expects.' This provides clear guidance on the tool's role as a precursor to render tools, effectively excluding misuse.

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