toggle_overage

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

Given the destructiveHint annotation, the description adds substantial behavioral context: billing rates, blocking behavior when disabled, and Pro-only availability. This goes beyond the annotation and clearly discloses consequences of toggling.

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 concise (four sentences), front-loads the main action, and every sentence provides valuable information—action, consequences, and eligibility/alternatives. No padding or 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 the simple tool with one boolean parameter and an output schema, the description covers the core behavior, pricing, eligibility, and alternatives. Minor gap: it does not explicitly mention what happens if a free user attempts to call the tool, but 'Only available for Pro tier' implies failure without specifying error behavior.

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 schema already fully describes the boolean parameter 'enabled' with 100% coverage, but the description adds meaningful context about what true/false actually does (continuing operations with billing or blocking operations). This enhances understanding 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?

The description clearly states the tool's function with a specific verb and resource: 'Enable or disable on-demand overage credits for Pro subscribers.' It distinguishes itself from other billing and toggle tools by detailing the exact behavior and eligibility.

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 provides clear context on when to use the tool (for Pro subscribers managing overage credits) and explicitly guides free users to alternatives ('buy credit packs or subscribe'). It lacks an explicit 'when not to use' for Pro users, but the enable/disable explanation effectively conveys usage decisions.

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