Get all numbers

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so "Read-only" merely repeats structured data. Beyond the HTTP route (GET /numbers) the description adds nothing — no mention of pagination behavior, filter interaction, or result ordering, even though page/per_page exist.

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?

Two terse sentences, front-loaded and free of padding. The only near-waste is "Read-only", which duplicates the annotation rather than adding new information.

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 nine-parameter listing endpoint with no output schema, the description should explain what a "number" record contains, how paging behaves (the schema itself warns per_page is not honored by every endpoint), and how results can be filtered. None of that is present, leaving the agent under-informed about invocation behavior.

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 100%, so all nine parameters (paging plus seven filter[...] fields) are documented in the schema itself. The description contributes no additional meaning about how filters combine or whether per_page is honored, so the baseline 3 applies.

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 ("Get all numbers") and the plural scope distinguishes it from the singular placetel_get_number sibling. However, it does not explicitly name any sibling or clarify how it differs from placetel_list_number_profiles or placetel_get_number.

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 when-to-use guidance, no prerequisites, and no mention of alternatives among the many number-related siblings (activate_number, deactivate_number, get_number, list_number_profiles). The agent must infer that this is the bulk-listing endpoint.

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