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

Annotations only declare readOnlyHint and openWorldHint=false, so the description carries the burden of disclosing real behavior, and it does: pdf_url is always null, PDF access is lead-gated behind a work-email form and client-side rendering, and no fetchable PDF bytes exist. This prevents a very likely agent failure mode that no annotation or schema field would reveal.

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 gating caveat are front-loaded, which is good, but the PDF discussion runs long and includes meta-commentary ('verified live: the marketing_reports.pdf_url column is unpopulated... an earlier version of this description incorrectly claimed...') that documents the description's own history rather than helping the agent act. A trimmer version could convey the same constraint in two sentences.

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 must explain returns, and it names the structured fields, content_html as the canonical body, the web URL, and the null/gated PDF fields. For a one-parameter read tool this is complete enough to call correctly and to answer follow-up user questions.

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 100% and the single slug parameter is already documented with examples, so the schema does the heavy lifting. The description restates the slug requirement but adds no format or normalization detail beyond what the schema provides — the correct baseline of 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?

States a specific verb and resource ('Fetch the full body of a published report by slug') and explicitly distinguishes itself from list_reports, which is named as the way to obtain the slug. An agent can select this tool without opening the schema.

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?

Opens with an explicit trigger ('Use when the user wants the full text of one published IndustryLens report') and states the prerequisite workflow ('after finding its slug via list_reports'). It also says what not to do ('Never construct or guess a .pdf URL yourself'), which is a concrete exclusion.

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