Update Reply Template

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

Description adds non-obvious behavior: 'If body changes, variables are re-extracted automatically.' Annotations already provide idempotentHint and destructiveHint, so this is additive.

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?

Description is short, front-loaded with main action, and uses a clear bullet list. Every sentence adds value.

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 7 parameters, no output schema, and moderate complexity, description covers return value ('updated template JSON') and key behavior. Missing some nuance but adequate.

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 low (43%), but description only lists parameters as optional without explaining semantics beyond what schema already provides. Does not compensate fully for coverage gaps.

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?

Description clearly states 'Update fields of an existing template' with a specific verb and resource. Distinguishes from siblings like 'replies_add_template' and 'replies_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?

Description mentions 'Only provided fields change' and auto re-extraction on body change, but does not explicitly state when to use vs alternatives or when not to use.

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