spawn_budget_status

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

The description discloses key behavioral details: data source (budget daemon), refresh rate, initial estimates for new tasks, and untracked tasks (pid=0). This goes beyond minimal expectations given no 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?

Three well-structured sentences: first states purpose, second adds usage guidance, third clarifies edge cases. No wasted words; highly efficient.

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 and an existing output schema, the description fully covers the tool's purpose, usage, and behavioral nuances. An agent can effectively decide when to invoke it.

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 tool has zero parameters, so the schema provides no parameter info. The description adds value by explaining the output context, making the baseline of 4 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?

The description clearly states the tool reports spawn-budget usage (cap, used, free, per-task RSS). It distinguishes from siblings like spawn_budget_set and spawn by focusing on status reporting for admission decisions.

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 explicitly says the tool is 'Used to decide whether another spawn() will be admitted,' providing clear context. It does not explicitly state when not to use or name alternatives, but the purpose is well-defined.

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