spawn_budget_set

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

No annotations provided, but description clearly states behavior: overrides cap, setting 0 disables enforcement, and does NOT persist across restarts. This adequately discloses behavioral traits.

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 with a use-case note; every sentence adds value. Front-loaded with action and unit.

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 1-parameter tool with output schema, description covers key aspects (action, parameter meaning, persistence, use cases). Minor gap: no mention of allowed range or default value, 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?

Schema has 0% description coverage for the single parameter. Description compensates by explaining 'limit_mb' is the spawn-budget cap in MB, adding meaning beyond the schema.

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 explicitly states 'Override the spawn-budget cap for this process (in MB)', using specific verb and resource. It clearly distinguishes from sibling 'spawn_budget_status' which would be for checking status.

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 when to use: 'when a heavy task needs a higher temporary ceiling' and 'drop the cap mid-session'. Also notes non-persistence and alternative for persistence via environment variable.

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