update_policy

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

States the replacement is complete, implying destructive overwrite, but with no annotations, description does not detail permissions, idempotency, or side effects like overwriting existing fields.

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 with no redundant information. Each sentence serves a clear purpose: stating the action and the required inputs.

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?

Offers basic completeness for a simple replacement tool with an output schema, but lacks details about payload requirements, error conditions, and behavioral nuances. Could be more informative.

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 description coverage is 0%, and description only names the parameters ('policy_id', 'full JSON payload') without explaining the payload structure or constraints, leaving agents to guess required fields.

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?

Description explicitly states 'replaces a detection policy completely', clearly indicating a full update operation. This distinguishes it from siblings like 'create_policy' (creates new) and 'delete_policy' (removes).

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?

Provides instructions to provide policy_id and full JSON payload, but no guidance on when to use this tool vs create or delete. Agents lack context to choose correctly among sibling tools.

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