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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds that results include contact details and cites the underlying endpoint (GET /vendors), which is mild extra context, but it says nothing about pagination behavior or result size, which matters for a paged list tool.

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, zero waste, with the resource definition front-loaded. It is perhaps too terse rather than padded, so the only deduction is that it under-delivers on guidance.

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 three-optional-parameter read tool with a fully documented schema and clear read-only annotations, the essentials are present. However, the description does not indicate whether the list is scoped to the account, how large result sets behave across pages, or what fields 'contact details' covers, leaving modest gaps.

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%: limit, offset, and business_name are each fully documented, including the hint to pass next_offset from the prior reply. The description adds nothing beyond the schema, 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?

States a specific verb and resource ('List vendors') and disambiguates the term by naming 'suppliers and contractors'. It does not distinguish itself from siblings such as upkeep_list_customers or explain why one would list vendors rather than customers, but the resource is unambiguous.

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?

The description only says what the tool does; it gives no when-to-use context, no prerequisites, and no mention of alternatives among the many list_* siblings. An agent must infer that this is the entry point for browsing vendors rather than searching for a specific one.

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