update_policy

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

Discloses that changes apply immediately with no approval step and that the operator can audit/revert. With no annotations, this level of behavior description is good, though it could mention auth requirements or rollback details.

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 focused sentences: first states purpose and effect, second gives usage and parameter guidance. Every sentence adds value, with no redundancy.

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 purpose, usage, behavioral impact, and parameter roles. Lacks mention of return value or error handling, but given the low complexity, it is nearly complete.

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%, baseline 3. The description adds meaning to the 'reason' parameter (logged but not gating) and ties all parameters directly to usage scenarios, exceeding the baseline.

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 states 'Updates the agent's own operational policy' with a specific verb and resource. It further clarifies the immediate effect and lists use cases, making the purpose unmistakable.

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 this when you need higher limits, more allowed tokens, or contract whitelisting to complete a mission.' Provides context for use but does not include explicit when-not-to-use or alternatives, which are less critical given the single sibling (get_policy).

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