Update Entry

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

With no annotations, description fully discloses key behaviors: PUT semantics, full payload requirement, no publish state change, and the public API continues serving the published snapshot. Also explains how to format relation and media fields.

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 concise: core action in first sentence, then critical behavioral notes and sibling differentiation. No unnecessary words.

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 no output schema, the description covers all necessary aspects: usage, behavioral traits, parameter details, and sibling differentiation. Complete for a mutation tool.

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 all parameters. The description adds valuable context beyond schema, especially for the 'data' parameter (richtext, relation, media field handling), increasing understanding.

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?

States 'Replace an existing content entry (HTTP PUT)' clearly identifying verb and resource. Distinguishes from siblings by naming patch_entry and publish_entry/unpublish_entry.

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?

Explicitly says use for full replacement, contrasts with patch_entry for partial updates, and clarifies that saves do not affect publish state, requiring explicit publish/unpublish calls. Also notes required fields must be included.

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