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

Annotations only declare readOnlyHint=true; the description adds real value by disclosing the pagination model ("Paged: pass next_page as page") and the underlying GET endpoint, so the agent knows this is a safe, paginated read. It does not describe default page size or ordering, which is the remaining gap.

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?

Front-loads the core operation, then filters, then pagination in three compact clauses with no filler. The raw endpoint path ("GET /public-api/v1/documents/") is marginally useful and the only low-value fragment.

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 six-filter, all-optional list tool with no output schema, the description covers what is listed, how to filter, what is returned (document metadata), and how to page – enough to invoke correctly. Defaults for missing filters and result ordering/limits are the only unstated details.

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%, so every filter's format (UUID for employee, YYYY-MM for period, ISO timestamps) is already documented in the schema. The description only restates the filter set at a higher level, adding no syntax or cross-parameter semantics beyond the baseline.

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 documents stored in Jet HR") and gives concrete content examples (payslips, contracts, other files) plus what is returned (metadata per document). It stops short of distinguishing itself from the very similar sibling jethr_list_payslips, which could confuse an agent choosing between them.

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?

Explicitly names the available filtering dimensions (employee, kind name, payroll period, last-update window), which tells the agent how to narrow results rather than dump everything. It offers no exclusion guidance or routing to alternatives such as jethr_list_payslips, so it sits at clear-context without alternatives.

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