update_agent

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

With no annotations provided, the description must disclose behavioral traits like mutability, idempotency, or side effects. 'Update an agent' reveals nothing beyond the operation name, failing to indicate whether it merges, overwrites, or has any destructive consequences.

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 extremely brief (three words), which is concise in length but lacks necessary substance. It does not earn its place because it adds no value beyond the tool name, making it under-specified rather than appropriately 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?

For a mutation tool with three parameters, no output schema, and no annotations, this description is severely incomplete. It provides no information on return values, required fields like patch, or behavior, making it inadequate for an agent to correctly invoke the 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?

The description adds zero insight into the patch object or id field, which are undocumented in the schema except for the workspace_id description. Schema description coverage is only 33%, and the description does not compensate for the missing parameter meaning.

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 a specific verb ('Update') and names the resource ('agent'), clearly identifying what the tool does. While it doesn't specify which attributes can be updated, it is unambiguous and distinguishes from sibling tools like create_agent, get_agent, and archive_agent.

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?

There is no guidance on when to use this tool versus alternatives such as create_agent or archive_agent. The description omits any context about partial updates, prerequisites, or when this is the appropriate operation.

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