resyncPayslipMonth

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

With no annotations, the description discloses the key behavioral trait: overwriting whatever is already stored. It also mentions that the PDF is fetched by default (and can be skipped via skipPdf). It does not mention return values or edge cases, but the critical overwriting behavior is clearly stated.

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 concise sentences: the first states the core action and scope, the second provides use cases and alternatives. No unnecessary words or repetition of schema details.

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 simple tool with a well-documented schema and no annotations, the description provides sufficient context: purpose, scope, overwriting behavior, and when to use it. The lack of return-value mention is a minor gap since no output schema exists, but the essential information is present.

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 has 100% parameter coverage with detailed descriptions for period, tenant, and skipPdf. The description does not add any new parameter semantics beyond what the schema already provides, 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 clearly states the tool re-fetches a single specific month's payslip data and PDF, overwriting existing stored data. It explicitly names the resource and scope, and distinguishes itself from syncPayslips by mentioning the alternative.

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 explicitly provides when to use this tool ('to retry one bad/truncated PDF, or to quickly check one month's numbers') and when not to ('instead of re-running syncPayslips over the whole history'), making the use case clear.

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