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

Annotations already declare the mutation/hint profile (readOnlyHint=false, idempotentHint=false, destructiveHint=false), so the description need not restate safety. It does add genuine value by disclosing that the output is a hosted server-side PDF with a 30-day URL lifetime, which the annotations do not convey. However, it says nothing about whether the artifact is stored, regenerated on repeat calls, or what happens after expiry, leaving meaningful behavioral gaps.

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?

A single efficient sentence with the key output fact (hosted URL, 30-day validity) front-loaded and no filler. It is appropriately sized, though its brevity comes at the cost of the missing usage and parameter guidance scored elsewhere.

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?

An output schema exists, so return-value detail is not required, but for an 11-parameter generation tool with 9% schema coverage and no usage routing, the single sentence is far from complete. The agent lacks guidance on required-field combinations and on how this differs from sibling report tools.

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 only 9% across 11 parameters, so the description carries most of the burden — yet it mentions no parameters at all. Nothing explains the place-vs-(latitude/longitude/timezone) anyOf requirement, the meaning of asOfDate, horizonYears, or timezoneOffset. The one enum-bearing parameter (chartStyle) is documented only in the schema.

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 gives a specific verb and resource ('Generates ... as a server-side PDF and returns a hosted URL'), which is enough to distinguish it from analytical siblings like analyze_chart_topic or calculate_dasha_system. It doesn't explicitly differentiate it from the other output-producing siblings (render_chart, generate_full_life_report), and 'the full reading context' is a somewhat vague object, so 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?

There is no statement of when to choose this tool over the many near-neighbor output tools (render_chart, generate_full_life_report, get_full_reading_context). No prerequisites, no exclusions, no alternative named. The agent is left to infer usage entirely from the name.

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