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

Annotations already cover readOnlyHint/openWorldHint, and the description still adds real value: pagination, the fact that routing callback URLs/emails are omitted from responses, and a prompt-injection caveat about untrusted message text. It stops short of explaining ordering or defaults, but the safety guidance beyond annotations is notable.

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 the core action, and every sentence carries distinct information (scope, omissions, endpoint, safety). No filler.

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?

With no output schema, the description should convey what a record contains; it names 'dedicated numbers and auto-reply settings' and what is omitted, which is a partial substitute. The two pagination parameters remain fully undescribed, leaving a clear gap for a tool an agent will call repeatedly.

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 limit and offset, and the description only gestures at pagination with 'a page'. It provides no defaults, ranges (1-100, 1-9999), or offset semantics, so it fails to compensate for the undocumented parameters.

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 a page of dedicated numbers and auto-reply settings') and names the endpoint. The word 'page' plus the omission note distinguishes it from the singular sibling smsglobal_get_dedicated_number without needing the schema.

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?

Usage is implied by 'page' (paginated listing) and 'Read-only', but the description never says when to choose this over smsglobal_get_dedicated_number or smsglobal_list_verified_numbers. No exclusions or prerequisites are given.

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