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

readOnlyHint=true already tells the agent this is a safe read. The description adds the returned field inventory and the underlying Buildium endpoint (GET /v1/vendors), which is useful context, but says nothing about pagination behavior, default ordering, or result caps beyond what the schema documents.

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?

Three tight sentences, front-loaded with the verb and resource, then filters, then endpoint. Nothing is padded, though the trailing API-path sentence is only marginally valuable to an agent that already has the tool contract.

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, zero-required read tool with full schema coverage and a readOnly annotation, the description covers the resource and the returnable fields adequately. It leaves pagination defaults and sort ordering entirely to the schema, which is acceptable but not fully 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%, so the schema already explains every parameter including the enum values and date formats. The description restates a subset of filterable fields (omitting last_updated_from/to, orderby, limit, offset) without adding syntax or semantics beyond the schema. 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 clarifies scope with synonyms '(contractors, suppliers)' plus the fields returned (contact details, category, insurance, default expense GL account). No sibling in the list covers vendors, so an agent can route here unambiguously.

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 enumerates filter dimensions ('name, email, phone, website, status or insurance expiration'), which implies when the tool is useful, but never states when to use it versus alternatives or any exclusions. Usage is inferable rather than stated.

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