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

Annotations already declare destructiveHint=true, idempotentHint=false, openWorldHint=false, so the safety profile is covered structurally. The description adds nothing operation-specific: it does not say whether disabling stops inbound/outbound traffic, detaches numbers, revokes credentials, or is reversible. The line 'No carrier settings change' is ambiguous and reads as if it belongs to the read/test-call tools rather than this destructive mutation.

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 a dense run-on paragraph of facts about sibling tools (passwords, verification calls, billed test calls, SIP OPTIONS), with the leading sentence 'Bring your own SIP trunk' occupying prime real estate while conveying nothing about this operation. Most sentences do not earn their place for this 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?

This is a destructive, non-idempotent mutation with no output schema and 0% parameter coverage, so the description must explain what is destroyed and what the agent should expect. Instead it provides family-level trivia, leaving the core question — what disabling does to the connection and its numbers — unanswered.

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 the two parameters (connection_id required, project_id optional), so the description carries the full burden and fails to compensate — neither parameter is mentioned or explained. It references 'numbers' and ownership flows, which are unrelated to the actual inputs.

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 never states what this tool does. It describes the SIP trunk family ('create, read or change a carrier SIP connection'), and the only indication of a disable action is the tool name/title. An agent reading only the description cannot distinguish disable_sip_connection from update_sip_connection, get_sip_connection, or delete_agent-style siblings.

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 text gives routing guidance for other tools — check_sip_connection_number_ownership, start_sip_connection_test_call, check_sip_connection_reachability — but says nothing about when to disable a connection versus updating or deleting it, nor what prerequisites or side effects select this tool. The relevant guidance for the tool being invoked is absent.

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