delete_policy

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

Discloses immediate loss of access for subjects/roles with the policy, a critical behavioral trait. No annotations provided, so description carries full burden. Lacks mention of permissions or reversibility.

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?

Single, efficient sentence with no wasted words. Front-loads the core action and adds essential consequence.

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?

Complete for a simple delete tool with one parameter and no output schema. Covers purpose and key side effect.

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 100%; description adds no extra meaning beyond the schema's 'Policy UUID' description. Adequate but does not elaborate on format or source.

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?

Clearly states 'Delete a policy by ID'. Specific verb and resource, distinct from siblings like create_policy, get_policy, list_policies.

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?

Describes consequence (immediately loses access) but does not explicitly state when to use this vs alternatives like unassign_policy. Provides implicit guidance but not explicit when-to-use or when-not.

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