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

readOnlyHint=true already tells the agent this is a non-destructive read, so the description only needs to add behavioral detail. It does reveal the data categories returned (contact details, emergency contact, address, leases), which is useful given no output schema exists, but it says nothing about pagination behavior, result volume, or rate limits.

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 tight sentences: the first front-loads what is returned, the second front-loads the filter dimensions, and the endpoint is appended last. No filler and no redundancy.

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 14-parameter, zero-required list tool with no output schema, the definition covers the resource, the filter surface, and the returned data categories, and annotations carry the safety profile. It leaves the return envelope (paging, total counts) unstated, which the absent output schema would otherwise have covered.

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 every one of the 14 parameters is already documented in the schema with matching semantics. The description's filter list merely restates a subset of those parameters (omitting limit/offset/orderby and date-range filters) and adds no syntax or interpretation detail beyond 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+resource ('List rental tenants') and enumerates the returned data (contact details, emergency contact, address, leases), plus the backing endpoint. It is clearly distinguishable from machinelike siblings, though it never explicitly contrasts itself with buildium_get_tenant, the singular counterpart an agent might otherwise pick.

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 lists filterable fields ('Filter by name, email, phone, unit number, property, owner, unit ids or lease term status') but gives no when-to-use context, no prerequisites, and no alternative-tool routing. An agent still has to infer that this is the bulk/collection counterpart to buildium_get_tenant.

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