spawn_budget_set

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

Discloses that the override does not persist across restarts, which is beyond the annotations (idempotentHint=true, destructiveHint=false). The description adds behavioral context without contradiction.

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 efficiently convey core action, persistence behavior, and usage examples. Every sentence earns its place, and key info is front-loaded.

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 simple one-parameter tool, the description covers purpose, side effects, and use cases. Output schema exists, so no need to explain return values. Definition is fully adequate.

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?

Despite 0% schema coverage, the description explicitly explains the single parameter (limit_mb) with units ('in MB') and special value behavior ('Set 0 to disable enforcement'), adding meaning beyond the schema's type-only definition.

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 uses a specific verb ('Override') and resource ('spawn-budget cap') with units (MB). It clearly distinguishes from siblings like 'spawn_budget_status' (view) and 'spawn' (execute).

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?

Provides explicit guidance on when to use (heavy task needing higher temporary ceiling, or dropping cap mid-session) and when not (for persistence, recommending the env var THREADKEEPER_SPAWN_BUDGET_MB).

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