allocate_budget

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

Describes algorithm and cost model but lacks explicit statement on side effects (e.g., read-only, no state modification). Without annotations, this is a gap for a computation tool that may be idempotent.

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, front-loaded with purpose, then formula, then usage guidance. No wasted words.

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 single param and no output schema, description adequately covers purpose, algorithm, and execution instructions. Could mention edge case (empty return if budget too small) but not critical.

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?

Adds significant value beyond schema: explains how 'minutes' is used as total budget, provides typical values, and ties to leverage formula for allocation decision.

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?

Clear verb+resource+method: 'greedy-allocates the highest-leverage subset of verification targets'. Leverage formula and cost estimates distinguish it from sibling tools like generate_verification_plan.

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 context: 'Use this when CI minutes are scarce or when an agent needs to pick what to verify before merging within a deadline.' Could improve by contrasting with alternatives like generate_verification_plan.

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