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

Annotations already cover readOnly/idempotent/non-destructive, so the description only needs to add context. It does: it discloses the access prerequisite ('Requires current operational company access') and that the response bundles a source snapshot alongside the report, neither of which is in the annotations. It does not explain failure behavior when access is absent.

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?

Two short sentences, front-loaded with the operation and scope, with the access requirement trailing. It is largely a restatement of the title, so it is efficient but adds little new phrasing beyond 'Requires current operational company access'.

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?

For a simple read-only getter with annotation coverage and no output schema this is close to sufficient, but with three required, entirely undocumented parameters it never tells the agent where the report UUID originates or how environment affects the lookup. That is a meaningful hole for an agent trying to invoke it correctly.

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% for all three required parameters. The description never mentions that 'report' and 'company' are UUIDs, nor what 'environment' selects between staging and production, nor where a valid report ID comes from (e.g., themes_list). With zero schema documentation, this gap should have been compensated and is not.

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 ('Read one') and a specific resource ('saved recurring-issue report and its source snapshot'), and the phrase 'including reports older than the latest list' implicitly separates it from summer_reports_themes_list. It does not name the sibling 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?

The 'older than the latest list' clause hints at when to reach for this over the list tool, but no alternative is named and no exclusion or precondition beyond the access note is given. Usage is inferable rather than stated.

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