Set policy rule

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

No annotations provided, so description carries full burden. It discloses that rules override defaults and higher priority wins, but does not detail persistence, immediacy of effect, or limit on rules per project.

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, immediately front-loaded with verb and resource ('Add an explicit policy rule'). Every word adds value; 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?

Tool has a nested object schema and 4 parameters with no output schema or annotations. Description covers core purpose and effect usage but omits details about match wildcards, priority range, and response format.

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 50%. Description adds meaning to effect (approve vs. block) and priority (higher wins), but does not elaborate on match fields beyond schema's 'Unset fields are wildcards' or the description parameter.

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 it adds an explicit policy rule that overrides defaults, with specific effects (allow/block). It distinguishes from siblings like list_policy_rules and check_policy by emphasizing rule creation and override behavior.

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?

The description provides usage context: 'Use this to approve something normally gated (effect:'allow') or to tighten further (effect:'block').' It does not explicitly state alternatives or when not to use, but the guidance is clear.

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