get_forwarding_profiles

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

The description details the return value (active profile and available profiles with routing rules) and implies a read-only operation. With no annotations, it adequately covers behavior, though it could mention if any permissions are required.

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 sentences, front-loaded with usage examples and essential return information. Every sentence adds value, and no extraneous content is present.

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?

Even without an output schema, the description fully explains the return data (active profile, available profile names, routing rules). For a simple tool with one parameter, it is complete and leaves no ambiguity.

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 input schema has 100% description coverage for the single parameter 'extension' with a clear example. The tool description does not add additional semantic meaning beyond the schema, so the baseline score of 3 applies.

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 explicitly states the tool returns the active profile name and all available profiles with routing rules for a given extension. It uses natural language queries to illustrate use cases, clearly distinguishing it from the sibling set_forwarding_profile.

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 specific example queries ('how are calls routed for extension 101?') and instructs to call this before set_forwarding_profile to see valid profile names, offering clear when-to-use and when-not-to-use guidance.

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