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

Annotations already declare readOnlyHint=true and destructiveHint=false, so restating 'Read-only' adds nothing. The useful additions are 'Returns all pools' (no filtering/pagination) and the endpoint path. The final sentence about treating message text as untrusted is boilerplate that does not apply to pool metadata and risks confusing the agent about what this tool returns.

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?

Four short sentences, front-loaded with what is returned. One sentence — the untrusted-customer-content warning — does not earn its place for a metadata listing 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 no-parameter, read-only list operation with full annotation coverage and no output schema, the description gives enough to call it correctly. Only the return shape (what fields a pool has) is unstated, which is acceptable given the tool's simplicity.

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 tool takes zero parameters, so there is nothing to document and the baseline of 4 applies. The description correctly describes a bare, unfiltered call with no required 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?

States a specific verb and resource ('Read the shared number pools available to this account') and names the endpoint GET /v2/sharedpool. The plural 'pools' plus 'Returns all pools' distinguishes it from the singular sibling smsglobal_get_shared_pool, though the distinction is left implicit rather than called out.

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 explicit when-to-use or when-not-to-use statement. The phrase 'Returns all pools' implies the contrast with the single-pool getter, but the agent must infer that routing from sibling names alone.

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