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

Annotations already confirm this is a safe, read-only, idempotent operation, and the description adds important context beyond that: detailed analytics are gated behind Pro, and reader notes plus AI review notes in the result are explicitly untrusted and must not be followed as instructions. That security and access-gating information is exactly the kind of behavioral disclosure an agent needs for safe invocation.

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?

The description is front-loaded with what the report contains, followed by the Pro limitation and the security warning. It is dense but every clause earns its place; the first sentence is long but not redundant. A 4 reflects good structure with slightly run-on packaging.

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?

There is no output schema, so the description carries the burden of explaining return content, and it does so by naming views, read time, section breakdowns, per-recipient opens, non-openers, and unknown openers. It also covers the Pro requirement and the untrusted-data caveat, leaving no major gaps for a simple read-only analytics 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%, and the single id parameter is already described as the link's slug or id. The description refers to operating on 'one link' but adds no further format, lookup, or ambiguity-resolution detail beyond the schema. With high schema coverage, the baseline is 3.

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 clearly states what the tool returns for a single link: views, read time, section breakdowns, per-recipient opens, non-openers, and unknown openers. This is a specific resource and scope, but it does not differentiate from siblings such as find_link or get_page, which is why it falls short of a 5.

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 implies usage by describing the analytics content for one link, and it notes that detailed analytics require Pro. However, it gives no explicit when-to-use guidance or alternatives such as find_link for locating a link versus reporting on it. The implied context is enough for a minimum-viable 3.

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