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

Annotations already establish readOnlyHint=true, so the safety profile is covered, and the description reinforces it by naming the underlying GET endpoint. It adds useful context about the fields returned and the contains-matching semantics of the location filter, though it says nothing about pagination limits or rate behavior beyond what the schema states.

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 compact sentences: purpose first, filters second, API mapping last. Every clause carries information and nothing is repeated or padded.

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 enumerates the returned fields, compensating for the missing return documentation. For an 11-parameter read-only list tool with full schema coverage, this is nearly complete, missing only details like paging defaults or result caps that a caller might want.

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, including limit/offset paging and the orderby syntax. The description's filter list largely restates those parameters, adding only the 'city/state contains' nuance already present in the schema, so the baseline of 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?

Names a specific verb (List) and resource (rental properties/buildings), and immediately clarifies the entity is buildings rather than units, which cleanly separates it from buildium_list_rental_units and buildium_get_rental_property. It also previews the returned fields, so the agent knows the shape of results before calling.

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, rental owner, property ids), which tells the agent when this tool is applicable. It stops short of naming alternatives or stating exclusions, so it is clear context without explicit routing guidance.

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