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

readOnlyHint=true already establishes the safe, non-mutating profile, and the description usefully discloses the API endpoint and that records include contacts and address. It adds no pagination or rate-limit context, but the schema already documents paging, so the incremental value over structured data is modest.

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, front-loaded with the verb and resource, with no filler. The endpoint reference is compact and earns its place; nothing is wasted.

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 simple read-only list tool with complete schema coverage and a readOnlyHint annotation, the description covers purpose, payload, and endpoint adequately. An agent has everything needed to invoke it correctly; only richer usage context is missing.

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 all six parameters (page, sort, filter, number, status, per_page) are fully documented in the schema itself. The description adds no filtering or sorting syntax beyond that, which is acceptable given the schema does the heavy lifting.

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 (List) and resource (vendors/suppliers) and notes the returned payload (contacts and address), so an agent knows exactly what it fetches. There is no competing vendor-list sibling, so no differentiation is needed, but it also does nothing to distinguish itself from the broader list_* family beyond the resource name.

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?

No when-to-use guidance, no mention of when this tool is preferable to searching clients via list_clients or filtering vendors by number. Usage is only implied by the tool name; nothing tells the agent how it fits in a workflow.

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