downloadCombinedPayslipsPdf

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

With no annotations, the description discloses the key behavioral trait: automatic splitting for long ranges due to a URL-length ceiling, including the approximate threshold (12-15 years). This adds value beyond the schema, though it doesn't cover failure modes or authentication requirements.

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 two sentences long: the first states the core purpose, the second adds a crucial caveat. It is well-structured and free of 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?

Given the tool's simplicity (3 parameters, no output schema), the description covers the main behavior and the split caveat. It doesn't explicitly state the return format, but 'Downloads ONE PDF' implies a file response, and the sibling tool context doesn't require more.

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 already provides descriptions for all three parameters (fromMonth, toMonth, tenant) with format examples. The description adds no further parameter-level detail, so the 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 states the tool's function: downloads one combined PDF for all payslips in a date range, explicitly contrasting with the per-month approach. This distinguishes it from sibling tools like syncPayslips or listTenants by focusing on the combined download use case.

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?

It provides context for when to use the tool ('handy for printing/sharing a multi-year span at once') and contrasts with per-month downloads. However, it does not explicitly name alternative tools or state when not to use it, though the 'instead of one file per month' hint covers this.

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