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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds useful constraints that no carrier settings change, number purchase, or phone call occurs, and notes a test-verification condition, but it leaves the list behavior itself opaque.

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 short, but it is not front-loaded with the actual list operation and spends sentences on side-effect exclusions and test verification rather than clarifying enumeration or pagination. The opening verb 'Manage' makes the structure misleading for a list tool.

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 read-only list tool with no output schema, the description should clarify what collection is returned, how offset works, and how project_id affects scope. It omits all of those details and instead focuses on constraints that are only loosely related to listing forwarding setups.

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 has two parameters with 0% description coverage, and the description does not explain offset pagination, its maximum, or whether project_id scopes results to a project. The parameter names alone carry all meaning, so the description fails to compensate for the schema coverage gap.

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 tool is named list_forwarding_setups, but the description says 'Manage an existing-number forwarding setup,' which does not state that it lists forwarding setups and uses a singular, management-oriented verb. This is vague and risks confusion with get_forwarding_setup or update_forwarding_setup, so it does not meet the specific verb+resource bar.

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 gives no explicit indication of when to use this tool versus get_forwarding_setup, create_forwarding_setup, update_forwarding_setup, or forwarding-test tools. The note that 'Test verification requires linked call evidence' is contextual but does not guide tool selection.

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