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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds useful signal by listing what fields come back (including payable balance), which matters because there is no output schema, but it says nothing about result volume, defaults, or ordering behavior beyond the word 'Paged'.

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?

Three terse fragments with zero filler, front-loading the resource and its fields before the paging note. Nothing could be removed without losing information.

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 no output schema, the description correctly compensates by listing the returned fields, and the schema covers all five parameters including archive semantics and paging defaults. Only the absence of guidance on total counts or result caps keeps it from a 5.

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 both enums and pagination bounds fully documented in the schema itself. The description adds no parameter-specific meaning beyond implying pagination, so the baseline 3 applies.

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 names a specific resource (vendors/suppliers) and enumerates the returned fields, so an agent immediately knows this is a paged vendor listing. It stops short of explicitly distinguishing itself from jurnal_get_vendor or jurnal_list_customers, relying on the name alone for that routing.

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?

'Paged. GET /vendors.' implies pagination usage, and the schema note about next_page reinforces it. But there is no explicit guidance on when to choose this over jurnal_get_vendor, or when to set include_archive, leaving retrieval strategy to inference.

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