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

Annotations already declare readOnlyHint=true, and the description confirms the read nature via 'GET /v1/rentals'. It adds the endpoint mapping but nothing about throttling, auth scope, result caps, or paging behavior; the safety profile is already carried by the annotation.

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 short sentences, front-loaded with the resource and returned fields, then filters, then endpoint. Efficient, though the filter sentence and the endpoint note are largely duplicating structured data rather than adding information.

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?

With no output schema, the description usefully names the returned shape (address, unit count, type/subtype, manager), which compensates for the missing return definition. An 11-parameter tool with all-optional filters is covered adequately, though paging/sorting behavior is left entirely to the schema.

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 parameter is already documented in the schema with enums, ranges, and formats. The description only restates a subset of filters in prose (and omits orderby, limit/offset, last_updated_from/to), adding no syntax or semantics 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 properties (buildings)') and even enumerates the fields returned, which distinguishes it from a single-property getter. The '(buildings)' gloss implicitly separates it from rental-unit tools, but no sibling is named outright, so it stops short of the top score.

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?

Enumerates the available filter dimensions (location, type, subtype, status, owner or property ids), which implies the browse/filter use case. However, it never states when to prefer this over buildium_get_rental_property or buildium_list_rental_units, nor any exclusions or prerequisites.

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