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

readOnlyHint=true already declares the safety profile, so the description need not restate it. It contributes the returned field set and the endpoint path, which is meaningful value given there is no output schema, but it says nothing about pagination behavior or how archived records interact with results beyond what the schema already states.

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?

A single compact statement with the resource front-loaded and no filler sentences. The field-list-plus-endpoint form is terse but every element carries 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 enumerated return fields are a useful substitute for a response contract, and all six parameters are fully documented in the schema. Only pagination semantics and filtering behavior are left implicit, which is a minor gap for a simple list tool.

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%, with enum values, defaults, and ranges all documented, so the baseline of 3 applies. The description adds no parameter syntax or filtering nuance beyond the schema.

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 identifies the resource (vendors/suppliers), enumerates the returned fields, and names the underlying endpoint, so an agent knows this is a vendor-listing read. It never uses an explicit verb but the resource and field list make the operation unambiguous and distinct from siblings like list_customers or list_items.

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?

There is no statement of when to use this tool versus alternatives, nor any prerequisites or exclusions. The sibling tools differ by resource, so an agent can infer some routing, but the description itself provides no usage context.

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