rendoc

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It clearly indicates this is a creation/mutation operation and mentions the output (template ID for use with generate_document). However, it doesn't disclose important behavioral traits like permission requirements, whether templates are editable after creation, rate limits, or what happens on duplicate slugs. The description adds value but leaves significant gaps for a mutation tool.

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 perfectly concise with two sentences that each earn their place. The first sentence establishes the core purpose with technical specifics, and the second provides crucial downstream usage context. There's zero wasted language or 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 this is a mutation tool with 11 parameters, no annotations, and no output schema, the description is somewhat incomplete. While it clearly states the purpose and provides usage guidance, it lacks important contextual information about permissions, error conditions, template lifecycle, and what the actual return value contains beyond 'template ID'. For a creation tool in a template management system, more behavioral context would be helpful.

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 documents all 11 parameters thoroughly with descriptions, enums, and defaults. The description adds minimal parameter semantics beyond the schema - it mentions HTML/Handlebars markup and JSON schema, which are already covered in the schema properties. The baseline of 3 is appropriate when the schema does the heavy lifting.

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 specific action ('Create a new reusable document template'), identifies the resource ('document template'), and distinguishes it from siblings by mentioning the output ('use the returned template ID with `generate_document`'). It provides concrete technical details (HTML/Handlebars markup with JSON schema) that differentiate it from other tools like list_templates or delete_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?

The description provides clear context about when to use this tool ('Create a new reusable document template') and explicitly mentions a downstream usage ('use the returned template ID with `generate_document`'). However, it doesn't specify when NOT to use it or explicitly compare it to alternatives like preview_template for testing templates before creation.

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