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

readOnlyHint=true already establishes this is a safe read, so the description's main addition is the underlying endpoint GET /vendors. It does not disclose pagination behavior, default sort order, or result-size limits — meaningful gaps for a list operation, but not contradictory to the annotations.

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 with the purpose front-loaded, followed by capability and endpoint. The sort/search enumeration largely duplicates the schema verbatim, a small amount of redundancy, but nothing is buried or bloated.

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 two-optional-parameter read tool with full schema coverage and no output schema, the definition covers how to call it. It falls short on what comes back (record fields, whether all vendors are returned, pagination), which an agent needs to plan a listing call.

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 both parameters are already documented in the schema, including the sort pattern. The description restates the same sort fields and search-by-name behavior with an example, adding essentially no meaning beyond the structured data; 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?

States a specific verb and resource ("List vendors") and adds the accounting synonym "(creditors)", which helps an agent map business language to the tool. It is distinguishable from siblings such as runmyaccounts_list_customers by the resource name, though it never explicitly contrasts with get_vendor or the customer list.

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?

Usage is only implied by the presence of sort and query controls; there is no statement of when to use this versus a detail lookup or other list tools, nor any precondition. An agent can infer "browse/search the vendor directory" but nothing more.

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