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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so the safety profile is covered. The description does add genuinely useful behavioral facts beyond that: passwords are write-only and never returned on reads, and verification calls are rate limited per number and per workspace. However, the framing "create, read or change" blurs a read-only tool's scope and implies write capability the annotations deny, and nothing is said about result ordering or pagination for a list operation.

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 first sentence is a family-level blurb that buries the actual list operation, and the rest of the text is devoted to four sibling tools' behaviors and billing/rate-limit notes irrelevant to a read-only listing. Nothing is front-loaded about what this call does or returns, so the reader must filter out unrelated material to find the one relevant clause.

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 simple two-parameter list tool with no output schema, the description should at minimum state that it returns SIP connections, that results are paginated via offset, and that project_id scopes the listing. Instead it spends its budget on mutation and test-call semantics of other endpoints, leaving the agent without the information needed to page or filter correctly.

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, so the description carries the full burden and does not meet it. Neither offset nor project_id is mentioned; there is no hint that results are paginated, what the page size is, or that project_id narrows the listing. An agent must infer both parameters from their names alone.

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 names the resource (carrier SIP connection and its numbers) and the backing endpoint (/v1/sip-connections), but the verb is a bundled "create, read or change" that covers the whole API family rather than this tool's actual operation. For a tool named list_sip_connections, the word "list" never appears and there is no statement about what set of connections is returned. An agent can guess it is the read path, but only by elimination.

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?

No guidance is given on when to call this tool rather than get_sip_connection, list_numbers, or create_sip_connection, all of which are siblings. The only routing information present concerns other tools — check_sip_connection_number_ownership, attach_sip_connection_number, start_sip_connection_test_call, check_sip_connection_reachability — which is useful for the family but does not tell the agent when this listing is the right call.

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