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

With no annotations, the description must carry behavioral transparency. It indicates a GET request and scoping, but 'Idle $0' and 'No DID sales' are cryptic and do not clarify side effects, costs, or rate limits.

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?

The description is short but includes confusing, seemingly unrelated phrases such as 'Idle $0' and 'No DID sales'. These extra fragments reduce clarity and make the description less focused than it should be.

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?

The description lacks important context such as expected response format, pagination behavior, or relationship to sibling call-related tools. The unclear phrases do not fill these gaps and may mislead an agent.

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 only parameter, limit, is fully described in the schema with range 1-100 and a default of 20. The description repeats the limit but adds no new semantic meaning, so the baseline score 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?

The description states that the tool lists recent calls and includes transfer path crumbs, and gives an endpoint. However, phrases like 'site + customer archive browser', 'Idle $0', and 'No DID sales' are unclear and obscure the core purpose.

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 description mentions scoping by 'x-temsor-pbx-key' but does not explain when to use this tool instead of related tools like pbx_calls_get, pbx_calls_graph, or pbx_search. No usage conditions or alternative selection guidance is provided.

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