Download bound book

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

The description adds valuable behavioral details beyond the annotations: output is base64-encoded, large exports are summarised, and an auditUser email is required. It also states 'Read', reinforcing the readOnlyHint. No contradictions with annotations.

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?

Three sentences, each providing distinct information: what the tool does, the auditUser requirement, and the return behavior. No filler or redundancy; front-loaded with the core purpose.

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 single-parameter read-only download tool, the description covers the essential details: purpose, required input, and return format. The only gap is that 'summarised' is vague and the nature of the returned file (e.g., file type) is not specified, but this is minor given the low complexity.

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?

The schema already fully describes auditUser (email format, override behavior, active user requirement), and the description largely restates these facts. It adds the general requirement that an auditUser email is needed, but no significant new parameter-level context. With 100% schema coverage, baseline 3 is appropriate.

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 clearly identifies the tool's function: generating and downloading the A&D bound book export. It uses a specific verb ('Generate and download') and resource ('A&D bound book export'), distinguishing it from sibling download tools like download_4473 or download_attachment.

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 first sentence establishes when to use this tool. It also mentions the need for an auditUser email, giving context on prerequisites. However, it does not explicitly name alternatives or state when not to use it, though the resource-specific wording makes the intended use clear.

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