get_additional_income_download_url

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

Annotations already mark the tool as readOnly and non-destructive. The description adds useful behavioral context beyond that: the returned URL is temporary, ephemeral, expires, and serves a PDF. This meaningfully informs the agent that the link cannot be persisted indefinitely.

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?

The description is short and front-loaded with the core action. The phrase 'ephemeral and expires' is somewhat redundant with 'temporary,' but overall the description contains only one extra clarifier and remains compact.

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 tool, the description provides enough context: it names the output format (PDF), the nature of the URL (temporary, public, expires), and the operation (get download URL). It does not state the expiration duration or error behavior, but these are not essential for initial tool selection.

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 input schema fully documents the single parameter 'id' as 'Additional income id' with 100% coverage. The description adds no extra parameter-level meaning, so the baseline score of 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 states a specific verb ('Get') and a concrete resource ('temporary public URL to download an expense document as PDF'). It is clear enough, though it does not explicitly differentiate itself from the sibling get_invoice_download_url and refers to 'expense document' rather than 'additional income,' which introduces slight ambiguity.

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 description implies when to use the tool: whenever a temporary PDF download URL for an additional income document is needed. However, it provides no explicit guidance about when not to use it, such as pointing to get_invoice_download_url for invoice documents or noting any prerequisites.

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