update_agent

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

No annotations provided, so description carries full burden. Covers conflict behavior (409 retry) and partial update pattern. Missing constraints like requiring draft state or side effects of updating a published agent.

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?

Two sentences, no redundancy. Purpose and key usage instructions are front-loaded. Could be slightly more structured but still highly concise.

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?

Covers core flow (read, conflict, partial update) but lacks details like enforcement of draft-only state, authorization requirements, and what the response contains (no output schema). Adequate but not comprehensive.

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 has 100% coverage, baseline 3. Description adds actionable context: expectedVersion should be read first, fields should be subset of changed fields in camelCase, going beyond schema definitions.

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 'Update a agent draft', indicating a specific verb and resource. It distinguishes from sibling tools like delete_agent, discard_agent_draft, and read_agent, making the purpose 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?

Explicitly instructs to read first for expectedVersion and handles 409 conflicts with retry, plus guidance to pass only changed fields in camelCase. Does not explicitly exclude scenarios or mention alternatives, but gives clear context for when to use.

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