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

Annotations already cover the safe/read-only and closed-world profile, so the bar is lower; the description earns credit by adding the Owner-only access restriction and the note that viewer data stays with the doc's owner. It does not mention caps or latency, but the auth/permission context is exactly the kind of thing annotations cannot express.

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?

Front-loaded with purpose and return contents, then usage intents, then the access caveat. Dense but every clause carries information; the long enumeration of returned fields borders on verbose relative to what the agent strictly needs.

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 steps up to describe the return payload, and it covers the owner-only constraint and doc identification. What remains unstated - pagination of the 'ten most recent viewers' or freshness of the stats - are minor omissions for a read-only tool.

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 100%, so all three parameters are already documented, including the fuzzy-matching note on doc_name and the 'this or slug' relationship. The description restates the doc_name/slug identification without adding format or fallback semantics beyond the schema, capping it at the baseline.

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 gives a specific verb+resource framing ('Who read a doc and how') and then enumerates exactly what is returned - share link, views, reading time, last-opened, recent viewers. It is clearly distinct from sibling reads like app_read_doc or get_doc_html, which fetch content rather than engagement stats.

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?

It names concrete user intents ('who saw it', 'how is it doing', 'what is the link') and even the downstream use case (material for a follow-up email), plus the access condition (Owner only). An agent has no ambiguity about when to pick this over the content-reading siblings.

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