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

With no annotations, the description carries the full burden and does well: it discloses cross-workspace scope, staff/session auth requirement, sort order, and two important privacy traits — numbers are masked and transcripts/recordings are excluded. It does not mention pagination behavior (limit/offset) or any rate limits, which a no-annotation tool ideally would.

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 tight clauses with the access constraint front-loaded, then scope, ordering, returned fields, and privacy limits. 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?

No output schema exists, so enumerating the returned metadata fields was necessary and is done, along with sort order and masking caveats. The one real omission is pagination — the tool exposes limit/offset but the description never explains that results are paged.

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%, so the description must compensate and largely does not. The listed items (workspace, direction, line, status, outcome, duration, charge) read as returned fields, not as documentation of the six parameters; the status/outcome/workspaceId filters and the since/limit/offset pagination controls are left entirely to the schema.

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?

Specific verb+resource+scope: lists call metadata across all workspaces, newest first, and gates it to platform staff with an account session. This clearly separates it from the workspace-scoped calls_list, though it never names that sibling explicitly.

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 gives a hard precondition ('Platform staff only (account session)'), which is useful routing information, but gives no explicit when-to-use-this vs calls_list guidance and no note on exclusions or when results would be empty.

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