download_announcement_pdf

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

With no annotations, the description carries the full burden, but it does disclose the key traits: this writes a file to disk (a mutation side effect) and returns the file path. However, it omits important behaviors such as whether an existing filename is overwritten, whether save_dir must already exist, and how download errors surface.

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 sentence that front-loads the action, names the destination parameter, marks filename as optional, and states the return value. Every clause earns its place with no filler.

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 strictly required (the description still confirms the file path is returned). For a write-to-disk tool with no annotations, the description covers source, destination, naming, and return, leaving only edge-case behaviors like overwrite/error handling unstated.

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%, so the description must compensate, and it does explain all three parameters: attachment (source object from get_announcements), save_dir (destination), and filename (optional override). It adds real meaning over the bare schema, though it doesn't specify path/filename format expectations.

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 ('Save') and resource ('an announcement's PDF') and explicitly identifies the input's provenance as the 'attachment' from get_announcements, which distinguishes it from read-only siblings like get_announcements and get_quote. An agent can tell exactly what this tool does without opening the schema.

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 parenthetical 'the attachment from get_announcements' effectively tells the agent when this tool applies and how to chain it after get_announcements. It provides clear context but no explicit exclusions or named alternative (e.g., what to do for non-PDF attachments).

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