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

Annotations already declare readOnly, idempotent, closed-world, non-destructive behavior, so the bar is lower and the description correctly does not repeat them. It adds genuinely new context the annotations cannot: the data is self-reported rather than verified identity, and results come in bounded pages — both material for how an agent should present or trust the output.

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?

Three short sentences, no filler, and the most decision-relevant constraint (explicit owner request only) is front-loaded. The 'Bounded pages' fragment is terse but informative rather than padding.

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 usefully names the returned fields (name/email/phone) and flags their self-reported nature, which is the key interpretive context. It is close to complete for a simple read, with pagination mechanics the only real gap.

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% across three parameters (id, limit, cursor), so the description carries the full burden. 'Bounded pages' hints that pagination exists but does not explain that limit caps at 50, that cursor is an opaque continuation token, or what the uuid id identifies — leaving the agent to reverse-engineer all three from the schema alone.

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 a specific resource ('captured leads of this document') and the title/name carry the read verb, so it is clearly distinguishable from siblings like get_document_stats, get_document_activity, or get_document_sharing. It stops short of restating the action explicitly, but the resource scope is unambiguous.

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 for captured leads of this document' is a real gating condition that tells the agent when not to call it (proactive/incidental use) and implies an authorization requirement. No sibling alternative is named for adjacent lead-like needs, so it falls short of a 5.

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