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

With no annotations, the description carries the full burden and does so well: it discloses that pdf_url is always null, that the PDF is gated behind a work-email lead capture and rendered client-side, and that no fetchable PDF bytes exist anywhere. It also warns against a concrete failure mode (constructing or guessing a .pdf URL), which is exactly the kind of non-obvious behavior an agent needs.

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 purpose and routing are front-loaded correctly, but the middle section is bloated with meta-narrative — a live-verification note about the marketing_reports.pdf_url column and an admission that an earlier description version was wrong. That changelog detail serves maintainers, not the calling agent, and the no-PDF point is restated more than once.

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 and no annotations, so the description must describe the return shape and the operational traps; it does both, naming content_html, the web URL, pdf_url, and pdf_download.url. Nothing an agent needs to call this correctly or to advise the user afterward is missing.

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 schema already gives the slug format with two concrete examples, so the baseline is 3. The description adds sourcing context by tying the parameter to list_reports output, which meaningfully reduces the chance of passing an unvalidated slug.

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 verb and resource — 'Fetch the full body of a published report by slug' — and enumerates what comes back (structured fields, content_html, web URL). It is immediately distinguishable from list_reports, which it explicitly positions as the slug-discovery step.

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 gives the triggering condition ('Use when the user wants the full text of one published IndustryLens report') and the prerequisite ('after finding its slug via list_reports'). It also defines the boundary case — the PDF is not obtainable through this tool, so the agent must redirect the user rather than call something else.

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