lemma_get_account_settlement_instructions

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

No annotations are provided, so the description carries the behavioral burden. It explains the two output modes (write to file via save_to, or base64-inline for small PDFs), but the qualifier 'small PDFs' is unexplained and behavior for larger PDFs is left ambiguous. It also does not mention authentication or error cases.

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?

Two sentences with no filler. The main purpose is front-loaded, and the conditional save_to behavior is stated clearly and compactly.

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 simple two-parameter download tool, the description covers the core operation and return behavior reasonably well. Since there is no output schema, it would benefit from clarifying what happens with larger PDFs and what success/error responses look like, but it is otherwise sufficient for straightforward use.

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 50%; account_id lacks a schema description. The description adds meaningful semantics for save_to (absolute path, file-writing behavior) and implies account_id through 'bank account's settlement instructions', but it does not fully compensate for the undocumented required parameter.

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 an explicit verb ('Download'), a specific resource ('a bank account's settlement instructions'), and the output format ('PDF'). This clearly distinguishes it from sibling get_* tools by naming the exact artifact being produced.

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 intended use is implied: call this when you need a bank account's settlement instructions as a PDF. It does not explicitly mention alternatives or when not to use it, though it does provide useful output-handling guidance via save_to versus inline return.

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