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

Annotations already declare readOnlyHint=true, idempotentHint=true and openWorldHint=false, so the safety profile is covered. The description adds some non-obvious scope constraints (no carrier settings change, no number purchase, no phone call), which is useful, but "Test verification requires linked call evidence" is cryptic and unexplained, and no auth or return behavior is described.

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?

Three short sentences with no filler, but they are not front-loaded around what the tool does. The final sentence about "linked call evidence" is an opaque fragment that costs space without adding usable guidance.

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?

There is no output schema and the description does not say what "instructions" contain, which is the core thing an agent needs for a retrieval tool. With both parameters undocumented in the schema and an unexplained test-verification clause, the definition leaves key behavior unaddressed despite the tool's modest complexity.

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 0% for both setup_id and project_id, so the description carries the full burden and fails: neither parameter is mentioned. Only the phrase "existing-number forwarding setup" loosely hints at setup_id, leaving project_id entirely unexplained.

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 name promises a retrieval ("get"), but the description opens with the verb "Manage," which is vague and conflicts with the read-only framing. It never says what "forwarding instructions" actually are or what the tool returns, so an agent cannot distinguish it from get_forwarding_setup, update_forwarding_setup, or record_forwarding_instructions.

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?

There is no statement of when to call this versus the many forwarding siblings (get_forwarding_setup, update_forwarding_setup, start_forwarding_test, record_forwarding_instructions). The sentences describe what does NOT happen rather than when this tool is the right choice.

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