list_templates

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

Describes the return type (JSON) and content (built-in templates and Overleaf integration details). Without annotations, the description carries burden; it discloses the output but does not detail structure or potential side effects. 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?

Very concise: three lines with front-loaded main action ('List available resume templates'). Every sentence adds value with no 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?

Covers key aspects: lists built-in and Overleaf info. Could detail Overleaf integration more, but given zero parameters and output schema existence, it is adequate. Sibling context is handled.

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?

No parameters, schema coverage 100%. As per rubric, baseline 4 is appropriate; description adds nothing needed since there are no 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?

Clearly states it lists available resume templates, specifically built-in ones for generate_resume and information on fetching additional templates from Overleaf. Differentiates from siblings like fetch_overleaf_template and browse_overleaf_templates by focusing on listing rather than fetching a specific template.

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?

Provides context on when to use: to see templates before generating a resume, and to get info on Overleaf templates. However, lacks explicit when-not-to-use or direct comparison to siblings, though the purpose is clear enough.

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