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

readOnlyHint=true already declares the safe read nature, so the bar is low, but the description adds almost nothing beyond the endpoint string. It omits return shape, pagination behavior (despite page_size/page_number params), and default ordering, which are exactly the sort of traits annotations do not cover.

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 terse sentences with zero padding, and the purpose is front-loaded before the API reference. Brevity here edges toward under-specification rather than waste, but nothing is superfluous.

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?

Annotations cover the safety profile and the schema fully documents all parameters, so the essentials are present for a simple filtered list. However, nothing is said about what a vendor record contains or how results paginate, leaving the description minimally viable rather than complete.

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 all eight parameters individually documented including defaults and max values. The description adds no filtering or sorting semantics beyond the schema, so the baseline 3 is appropriate.

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 ('maintenance vendors'), and the API endpoint confirms it is a read of /vendors. It is distinguishable from siblings like doorloop_list_owners or doorloop_list_tenants by resource, though it does nothing explicit to differentiate itself.

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 guidance on when to use this tool, what prerequisites exist, or what alternatives might apply. An agent must infer that this is the listing endpoint for vendors purely from the name.

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