public_access_report_pdf

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

Annotations are absent, so description must carry full burden. It says 'via web session' but does not explain if this is a read-only operation, whether it modifies state, or if any side effects occur (e.g., session creation). No disclosure about persisting the downloaded file.

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?

Description is very concise with two sentences, no redundant text. The route is front-loaded. However, it could be expanded with parameter context without losing conciseness.

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?

With 4 parameters, no output schema, and no annotations, the description is incomplete. It fails to explain the meaning of 'web session', how to specify the ids parameter, or what the tool returns (e.g., file path or bytes). This is insufficient for correct invocation.

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 only 25% (only report_name has a description). The tool description adds no parameter information. It does not explain the route parameters (report_name, doc_ids) or the connection and save_path fields, which are critical for correct usage.

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?

Description states 'Download PDF report' with a specific resource (PDF report) and verb (Download), and mentions the route. It distinguishes from related report tools like public_access_report_html by implying a PDF format, but does not explicitly differentiate from similar download tools like public_access_download.

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?

No guidance on when to use this tool versus alternatives (e.g., public_access_report_html or public_access_report_xlsx). The description does not mention prerequisites, such as needing an active web session, or conditions like required authentication.

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