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

Annotations already declare readOnlyHint=true, so the safety profile is covered and the bar is lower. The description adds the upstream endpoint (GET /v1/vendors) and the returned field set, but says nothing about pagination behavior, result caps, or rate limits — despite the tool having limit/offset parameters.

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 compact sentences plus an endpoint reference; the core purpose is front-loaded and nothing is padded. The trailing "Buildium: GET /v1/vendors" is a small but non-wasteful implementation anchor.

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 an 11-parameter, read-only list tool with no output schema, the description covers purpose, filter surface, returned fields and the underlying endpoint. What it lacks — pagination and ordering guidance — is already captured in the schema, so an agent can call it correctly.

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 11 parameters are documented in the schema and baseline is 3. The description reinforces the free-text 'contains' filters (name, email, phone, website) and status/insurance windows, but omits limit, offset, orderby and the last_updated range — adding only marginal value over 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?

States a specific verb and resource and disambiguates the domain term by glossing vendors as "contractors, suppliers". It also enumerates the payload fields (contact details, category, insurance, default expense GL account), so an agent can distinguish it from sibling list tools like list_tenants or list_rental_owners without opening the schema.

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 names the filterable dimensions (name, email, phone, website, status, insurance expiration), which implies when the tool is useful, but it gives no explicit when-to-use/when-not guidance and does not point at any alternative sibling. Adequate but leaves routing to inference.

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