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

The readOnlyHint annotation already establishes that this is a safe read-only operation. The description adds useful context by naming the returned fields and the Buildium endpoint, but it does not disclose behavioral details such as pagination defaults or rate-limit behavior beyond what the schema already provides.

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, with the core purpose front-loaded and the endpoint appended with no wasted wording.

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 simple list tool with read-only annotations and a fully described schema, the description is largely complete: it identifies the resource, returned fields, filtering, and endpoint. It could do slightly more to distinguish the list operation from its singular sibling, but no critical information for calling it correctly is missing.

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 six parameters are already documented in the schema. The description's 'Filter by property' is a mild restatement of the property_ids filter, adding no syntax or meaning beyond the structured field.

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?

The description gives a specific verb (List) and resource (rental units), plus a concrete list of returned fields. It does not explicitly differentiate itself from the singular sibling buildium_get_rental_unit or from buildium_list_rental_properties, so it stops just short of a 5.

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 only usage hint is 'Filter by property,' which is closer to a parameter note than guidance about when to select this tool. There is no mention of when to use it versus alternatives like buildium_get_rental_unit or buildium_list_rental_properties.

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