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

Annotations already declare readOnlyHint=true, openWorldHint=true, destructiveHint=false, so the safety profile is covered. The description adds real behavioral context beyond that: the read-only listing endpoint, the key-type-dependent visibility scope, and the shape of the payload. It omits ordering, default page cursor semantics and whether inactive numbers are returned, keeping it out of 5 territory.

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?

One compact paragraph: the returned-field inventory comes first, the key-scoping rule second, the endpoint last. No filler, no repetition of the title, and every clause carries information the agent needs.

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 compensates by enumerating the fields the response carries, and pagination is handled by the schema's page/per_page descriptions. For a zero-required-parameter list tool with annotations covering safety, this is nearly complete; only ordering and pagination defaults are unaddressed.

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 four parameters (page, per_page, account_id, profile_id) are already documented in the schema, including the 'Agency key only' restriction. The description restates the agency/profile filter semantics with no extra format or boundary detail, 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 ("List the call-tracking numbers") and then enumerates the returned fields — tracking/destination number, call flow, trigger, recording and messaging flags, last used. That is enough to separate it from the list_* siblings (list_leads, list_profiles, list_web_forms) without opening any schema, and the GET /tracking/numbers endpoint pins the resource precisely.

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?

Explains the key-dependent scoping: a Profile key lists only its own profile, while an Agency key may filter by account_id/profile_id. That tells the agent when the filter parameters are usable, which is the main usage decision here. It does not name an alternative tool (none exists among the siblings) or state exclusions, so it stops short of a 5.

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