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

Beyond the annotations (readOnlyHint=false, destructiveHint=false), the description reveals meaningful side effects: accepting records the reward against the funded escrow and omitting a reward defaults to the program's tier for the assigned/reported severity. This adds behavioral context that annotations alone do not provide.

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 deliver the core purpose, decision options, reward behavior, and ownership constraint without wasted words. The most important information is front-loaded in the first sentence.

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 transactional decision tool with five parameters and no output schema, the description covers the role, decision values, accept side effects, default reward logic, and authorization constraint. It does not describe what happens after non-accept decisions (e.g., notification or status change), but the schema and annotations fill most gaps, so the missing piece is minor.

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 input schema already has 100% description coverage, so the baseline is 3. The description adds a small amount of extra meaning by clarifying how the reward default works ('assigned (or reported) severity') and linking acceptance to escrow, but it does not substantially enrich any parameter beyond what the schema already states.

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 leads with a specific verb ('decide on a submission') and enumerates the four decision options (accept, reject, duplicate, spam). It immediately distinguishes the tool from siblings by scoping to program owners and adds the accept behavior of recording the reward against funded escrow. This leaves no ambiguity about what the tool does.

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 clearly states the intended role ('As a program owner') and imposes an explicit constraint ('Only works on programs you own'), which tells an agent when the tool is usable. It does not name alternative sibling tools or explicitly say when not to use this tool, so it stops short of a 5.

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