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

No annotations are provided, so the description carries the full behavioral burden. It does add genuine value by disclosing the auth precondition (platform staff, account session), which is the kind of information annotations would otherwise supply, but it says nothing about read-only vs mutating behavior, pagination semantics despite limit/offset params, or return content.

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 short fragments, front-loaded with the access constraint, with no filler. It is appropriately sized but reads as under-specification rather than compression; there is no wasted text but also very little structure to guide invocation.

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 listing tool with no output schema and no annotations, the description should reveal what the list returns (entities, phone numbers, pagination behavior). The staff-only constraint is covered, but the return content and the relationship to the add/remove siblings are left entirely unspecified.

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% and the description adds no parameter information at all. The two parameters (limit, offset) are conventional pagination fields whose defaults and bounds the schema already encodes, so an agent can infer their use, but the description does nothing to compensate for the absent descriptions.

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 a specific domain resource ('SAGOT's platform do-not-call list'), which is more than a bare restatement of the tool name and implicitly distinguishes it from siblings platform_blocklist_add and platform_blocklist_remove. However, it never states a verb (list/retrieve) or what the list contains, so the agent must infer the operation from the name 'list'.

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?

The only guidance is an audience restriction ('Platform staff only (account session)'), which is a prerequisite rather than a when-to-use statement. Nothing indicates when to call this versus the add/remove siblings, or what constitutes the blocklist being returned.

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