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

Annotations already establish readOnly/idempotent/non-destructive, so the bar is lower, yet the description adds genuinely useful data caveats: bounded pagination, verified vs self-reported emails, non-retroactive anonymous identification, non-unique visits, and approximate duration. These materially shape interpretation of results. It stops short of describing page size or exhaustion behavior.

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?

Terse and dense with no filler; the constraint leads. It reads as a packed set of clauses rather than a structured purpose-then-caveats flow, but nothing is wasted.

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 should help the agent understand the return payload; it supplies valuable interpretation caveats (visit semantics, email provenance, duration accuracy) but not the structure or fields returned. Adequate but leaves the agent guessing about output shape and pagination mechanics.

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 0%, so the description carries the burden for id, limit, and cursor. 'Bounded pages' vaguely gestures at pagination but never explains that limit caps page size (max 50) or what cursor does. The required document id is not described at all. Significant compensation gap.

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 references 'detailed reader activity' for a document, which conveys the resource but not a clear verb or the returned shape. It never distinguishes this tool from siblings like get_document_stats or get_document_leads, which likely overlap in the 'activity' space. Purpose is inferable but not precisely stated.

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?

'Only use on an explicit owner request' is a strong, explicit when-to-use gate that most definitions lack. However, it names no alternative tool (e.g., get_document_stats for aggregate numbers) and gives no when-not condition beyond the owner-request constraint.

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