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

readOnlyHint=true already tells the agent this is a safe read, so the description's main contribution is the entitlement gate, which is genuinely useful and not in the schema or annotations. It says nothing about pagination defaults, result ordering, or what a page of results looks like beyond the schema's own next/limit hints.

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 sentences: the operation and its entitlement gate first, then the available filter axes. No restatement of the title and 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?

For a read-only paginated list with no output schema, the definition covers the operation, the access prerequisite, and the filter surface, which is most of what an agent needs. The remaining gap is the unmentioned contactNumber parameter and any hint about what a content-analysis result contains, but neither blocks a correct call.

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 coverage is 63%, and the description adds a semantic grouping ('filter by time, source, participant or artifact name') that maps loosely onto since/before, sourceId, participantId and artifact. It does not mention contactNumber at all, nor how the time window relates to recording vs. transcript start, so the uncovered parameters stay covered by neither source.

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 AI content-analysis results') that an agent can act on immediately. However, the sibling set contains both spokephone_list_call_content_analysis and spokephone_get_content_analysis, and the description makes no attempt to distinguish this tool from either, leaving the agent to guess which listing is appropriate.

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?

'Needs the Enlighten entitlement' is a real prerequisite that prevents a failed call, and the filter dimensions hint at how the tool is scoped. But there is no statement of when to prefer this over list_call_content_analysis or get_content_analysis, so the routing decision is left implicit.

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