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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description contributes only the content scope (contractor payment invoices); it says nothing about result volume, pagination, or default limit behavior. Adequate but not additive.

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 short sentences with the purpose front-loaded and no padding. The second sentence partially restates the first ("Shows contractor payment invoices" vs. "Get invoices"), which is mild redundancy but it also narrows scope usefully.

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?

With three optional params and no output schema, the description should at least hint at what comes back or how results are bounded. Annotations cover the safety profile, but an agent gets no signal on return shape, ordering, or whether the default limit of 20 applies silently.

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 100%, with limit, company, and statuses fully documented in the schema itself. The description adds no parameter meaning beyond that, which is the expected baseline when the schema does the work.

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 and resource (get invoices) scoped to the Deel account and to contractor payment invoices, which separates it from the generic get_invoices. It never names the closest siblings (deel_get_payment_receipts, get_invoices) for explicit contrast, so a 4 rather than a 5.

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?

"Use when the user asks about Deel payments, contractor invoices, or payment history" gives a clear triggering context. It offers no exclusions or alternative-tool routing, such as when to prefer deel_get_payment_receipts, so it stops short of a 5.

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