set_forwarding_profile

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It marks the tool as '[DESTRUCTIVE]' and states changes take effect immediately and require user confirmation. However, it does not detail side effects, reversibility, or what exactly is overwritten, leaving gaps.

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 very concise, using a warning tag and two sentences to convey purpose, usage, and key constraints. It front-loads the destructive nature and provides examples without unnecessary detail.

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 tool has no output schema and no annotations, the description covers essential aspects: purpose, usage, valid inputs, immediate action, and prerequisite. It does not describe the return value or error behavior, but for a simple two-parameter tool, it is reasonably complete.

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 describes both parameters with examples. The description adds value by listing valid profile names and advising verification via get_forwarding_profiles, which clarifies the expected format and provides actionable guidance 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 that the tool is for changing call routing, with explicit examples like 'set extension 101 to Away'. It distinguishes itself from the sibling tool 'get_forwarding_profiles' by indicating it is for modification, not just viewing.

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 guidance on when to use the tool ('when the user wants to change call routing') and includes a directive to call get_forwarding_profiles first to verify profile names. However, it does not explicitly mention when not to use it or suggest alternative tools for related actions.

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