veto_learning_apply

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

Annotations provide no safety clues (readOnlyHint=false, destructiveHint=false). Description adds that thresholds are 'applied' and router 'immediately uses' them, indicating a state change with immediate effect, which is valuable beyond annotations.

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, 28 words, front-loaded with action and condition. Every sentence provides essential information 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?

Given no parameters, no output schema, and simple action, the description fully explains purpose, prerequisite, and immediate consequence. No missing information for an agent to invoke correctly.

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?

No parameters, so schema coverage is trivially 100%. Rubric baseline for 0 params is 4. Description adds no param info (none exist), so score is appropriate.

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 clearly states the tool applies learned tier thresholds to the router, with specific conditions (20 outcomes) and effect (immediate use on next veto_route_task). Distinct from siblings like veto_learning_stats or veto_record_outcome.

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?

Explicit prerequisite of 20 recorded outcomes guides when to use. Does not mention when not to use or alternatives, but sufficient for this straightforward tool.

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