Update Site Content

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

Annotations indicate idempotentHint=true and destructiveHint=false. The description adds important behavioral context beyond annotations: it warns that the full value must be sent, implying that a partial value will overwrite the existing data. It also instructs to read first to understand value shapes, which is a safety measure. This adds meaningful behavioral nuance without contradicting 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 two sentences, front-loaded with the core action ('Set the JSON value'), followed by a necessary prerequisite. Every word earns its place; no redundancy or fluff.

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 the tool's simplicity (two parameters, no output schema, low complexity), the description covers the key behavioral aspects: what it does, what to do first, and what to send. It leverages the annotations for idempotency and non-destructiveness. No critical information is missing for an agent to use it correctly.

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 100% with descriptions for both key and value. The description adds the crucial semantic that value must be the full new value, not a patch. This goes beyond the schema's generic 'stored as the new content' phrasing, helping the agent understand the replacement semantics.

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 uses the specific verb 'Set' and clearly identifies the resource: 'the JSON value for one site content key.' This distinguishes it from reading operations like get_site_content and from page-specific updates like update_page_content. The purpose is unambiguous.

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 guidance to read get_site_content first and to send the full new value, establishing a necessary prerequisite. It does not explicitly exclude alternatives or name when not to use the tool, but the instruction to read first implies a safe workflow. Lacks explicit alternative naming but enough for practical use.

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