update_entry

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

The description explains the partial update behavior ('Only the fields included in the data JSON will be modified'), which adds context beyond the annotations. It does not cover failure modes or authorization, but annotations already provide safety hints.

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?

Three concise sentences: core purpose, behavioral detail, and usage advice. No redundancy or verbosity.

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 complexity (partial update), the description adequately explains behavior and prerequisites. An output schema exists, so return values are covered. No gaps for agent invocation.

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%, so baseline is 3. The description adds value by explaining the partial update pattern for the 'data' parameter and suggesting a workflow, going beyond the schema descriptions.

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 action ('Update an existing content entry by its ID') and specifies the method ('with partial or full field data'), effectively distinguishing it from sibling tools like create_entry or delete_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?

The description advises using get_entry first to see current values and provides a clear pattern for partial updates. However, it does not explicitly mention when not to use this tool or compare with alternatives like bulk_action.

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