update_template_content

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

The description explicitly discloses destructive behavior (clearing the template with an empty body) and concurrency protection for append/prepend, aligning with the destructiveHint=true and readOnlyHint=false annotations.

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 concise, using two sentences to convey the primary purpose and important behavioral nuances without unnecessary detail.

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?

The description adequately covers the tool's side effects and failure modes, which is sufficient for an update operation with no output schema, though it could mention the absence of a return value or error conditions.

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 schema describes only 3 of 4 parameters; the description adds context for body (clearing) and mode (concurrency protection) but does not mention collectiveId, leaving a gap in understanding its purpose.

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 (writing the markdown body of a page template) and its role in create_page, distinguishing it from the related update_template tool that handles other template properties.

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?

It explains when to use the tool (to set template content), describes edge cases (empty body clears the template) and concurrency behavior for append/prepend, though it does not explicitly mention when not to use it or contrast with update_template.

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