Update a press release

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

With no annotations, the description transparently conveys behavioral details: partial updates, the email side effect, membership requirement, and error for free accounts. This is more than adequate.

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 and well-structured, using two sentences to cover core behavior, side effects, and constraints without unnecessary 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 absence of annotations and output schema, the description sufficiently covers what the tool does, key side effects, and failure conditions. No critical information is missing.

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 provides descriptions for all parameters, and the description adds key context about partial updates and the status side effect. This enhances understanding beyond the schema alone.

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 tool's purpose: partially updating an existing press release. It distinguishes from creation and posting by emphasizing 'only supplied fields change' and the ownership requirement.

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 implies when to use it (when updating existing press releases) and notes important side effects (status 1 emails followers) and prerequisites (paid membership). However, it doesn't explicitly contrast with sibling tools like post_press_release, but the phrasing is sufficient for most cases.

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