delimit_cost_controls

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

Lists side effects: actions 'set' and 'reset' mutate state, 'status' and 'quota' are read-only. Since no annotations exist, description carries full burden; it covers the key behavioral distinction among actions.

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?

Well-structured with clear sections (purpose, when to use, when not, sibling contrast, side effects). Every sentence adds value; no redundant text.

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?

Covers purpose, usage, side effects, and sibling differentiation. No annotations provided, but description sufficiently guides selection and invocation. Output schema exists but isn't needed to explain returns.

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%, so baseline is 3. Description mentions actions and that tool_name is required for certain actions, but adds minimal extra 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?

Clearly states 'Manage MCP rate limits and session cost controls' with specific verb and resource. Differentiates from siblings like delimit_cost_analyze and delimit_cost_alert.

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?

Explicitly provides when to use (inspect/adjust), when not to use (project-cost analysis, alert configuration), and names alternative tools (delimit_cost_analyze, delimit_cost_alert).

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