set_rate_profile

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

With no annotations provided, the description must carry the full behavioral disclosure burden. It adds two key traits: the index is 0-based and the change requires an explicit cli_save to persist. This is valuable context beyond the input schema, though it could mention what 'active' means or any side effects.

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?

Two sentences with zero waste. The first sentence states the primary action, and the second provides a critical follow-up step. Information is front-loaded and 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 simple one-parameter tool with no output schema, the description is largely complete: it explains the main action, the 0-based indexing, and the persistence requirement. It lacks a brief explanation of what a rate profile is, but the tool name and domain make it reasonably clear.

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 description coverage is 100% (the 'index' parameter already documented as '0-based, typically 0–5'). The description reinforces '0-indexed' but adds no new semantic meaning beyond what the schema provides, so baseline 3 is 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 action ('Switch the active rate profile') and specifies it is 0-indexed. It distinguishes this tool from other 'set_*' sibling tools by focusing specifically on rate profiles, making the 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 implies when to use the tool (to switch the active rate profile) and provides a follow-up instruction to call cli_save to persist. It does not explicitly exclude alternatives or provide when-not-to-use guidance, but the clear verb and resource make usage context obvious.

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