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

Discloses non-obvious behavior well beyond the annotations: PDFs are purged after 24h, stale entries come back with expired: true and a dead URL, and limit defaults to 10 with a 1-50 range. However, it claims 'Free to call' while the same block says cost is not in the public credit manifest, and it never explains why annotations mark this list as readOnlyHint=false — an ambiguity an agent would want resolved.

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-loads purpose, then usage, then lifecycle behavior, then cost, in three dense sentences with no filler. The appended [Group]/[Cost] tags add some clutter and the internal free-vs-cost tension slightly muddies the close.

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 list endpoint with an output schema, the description covers what an agent needs: scope, expiry semantics, pagination default and cost posture. The remaining holes are the unexplained readOnlyHint=false and the fact that the advertised limit parameter is not actually accepted by the schema.

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%, so the two declared parameters (fields, precision) are already documented and the description adds nothing about them. It does add limit semantics (1-50, default 10), but that parameter is absent from the input schema, so the extra detail creates a mismatch rather than compensating for a gap.

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 (List) and resource (the calling key's recently generated PDF reports) and enumerates the returned fields. It is clearly distinguishable from the many sibling astroway_reports_* tools, which generate reports rather than list past exports.

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?

Gives two concrete usage contexts: re-fetching a report link inside its 24h validity window and surfacing recent exports in a dashboard. It does not name an alternative tool or state when not to use it, so it falls short of explicit routing guidance.

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