clear_spend_limit

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

With no annotations provided, the description carries the full burden of disclosing effects. It clearly states the action, the post-condition (only bounded by creditLimit), and the authentication requirement (agent key). This exceeds a bare 'clears the spend limit' and provides meaningful behavioral context, though it could go further (e.g., reversibility).

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 two short sentences, front-loading the core action ('Remove the agent's session spend cap.') and adding essential context ('Requires an agent key') without any filler. Every word earns its place.

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 parameterless tool with no output schema and in the context of a balanced set of sibling tools, this description is complete. It covers the action, the impact on future behavior, and the necessary authority, leaving no obvious gaps for an agent to miss.

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, making schema coverage trivially 100%. No parameter documentation is needed, so the baseline of 4 applies. The description correctly focuses on the action and its effects instead of parameters.

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 states a specific verb ('Remove') a specific resource ('the agent's session spend cap') and clarifies the resulting boundary ('Subsequent paid calls will only be bounded by the on-chain creditLimit'). This clearly distinguishes it from sibling tools like set_spend_limit and get_spend_limit.

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 implies the use case: when you want to lift the session cap but still be bound by the on-chain credit limit. It also provides a prerequisite ('Requires an agent key'), which is useful guidance. However, it does not explicitly mention when not to use this tool or name alternative tools, so it misses the top tier.

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