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

With readOnlyHint=true already covering the safety profile, the bar is lower, and the description adds real context: results are paged and 'next_page' from the prior reply must be passed as 'page', plus the underlying endpoint. It stops short of describing result shape or any rate/scope limits, which keeps it from a 5.

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 zero waste: purpose and optional filters first, pagination and endpoint second. Nothing is repeated or buried.

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 read-only paged list tool with five optional params and no output schema, the description covers what it returns in general terms ('contractors and their collaborations'), all filter dimensions, and the paging contract. Only a brief note on the response envelope would make it complete.

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 coverage is 100%, so all five parameters are already documented in the schema. The description's phrasing of the date 'window' and the contractor/employee filters restates what the schema says, adding no new formatting or edge-case semantics beyond it.

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 ('List external contractors (collaborators) and their collaborations') and names the filter axes, so the scope is unambiguous. It does not explicitly contrast itself with the sibling jethr_get_contractor, which an agent could confuse for fetching a single contractor's details.

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?

Says the results are 'optionally filtered by contractor, linked employee or a collaboration date window', which implies when the filter params are useful. However, it never states when to use this list tool versus jethr_get_contractor for a single record, nor any exclusions or prerequisites.

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