chimera_budget_lock

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

Without annotations, the description conveys key behaviors: it returns remaining_tokens and status (ok/warn/critical), and instructs compression when critical. This goes beyond basic locking, though it could detail side effects or error scenarios.

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?

The description is four sentences, front-loaded with the primary purpose, then lists actions, returns, and a conditional behavior. Every sentence adds distinct value 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 4 parameters, 100% schema coverage, and no output schema, the description covers all actions, return values, and a critical behavior. It lacks output schema details but that is not required. Adequate for the tool's complexity.

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 coverage is 100%, but the description adds meaning: it connects max_output_tokens to chimera_csm, explains tokens_generated as 'this turn', and clarifies action enum values. This enhances understanding beyond the schema alone.

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 manages token budgets after CSM proposal approval, with four distinct actions (lock/check/update/release). It distinguishes itself from siblings like chimera_budget by focusing on post-approval locking, making purpose unambiguous.

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 indicates the tool is used 'after user approves CSM proposal' and lists available actions, providing clear context. However, it does not explicitly specify when to use this tool over alternatives like chimera_budget, leaving some ambiguity for an AI agent.

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