Buildium List Units

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds meaningful behavioral context beyond annotations by warning that pagination means one page is not the whole collection, which is critical for counting/aggregation tasks. This is a valuable disclosure that the annotations do not provide.

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?

The description is two sentences with no filler. The core purpose is front-loaded, and the pagination warning is placed second where it can influence invocation behavior. Every sentence earns its place.

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 read-only list tool with strong annotations and an output schema, the description covers the main behavioral caveat (pagination) and the primary filter (property_id). It does not explain the remaining parameters, but the schema provides names, types, and defaults, and the output schema covers return structure. The description is complete enough for correct invocation in most cases.

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 0%, so the description must compensate for parameter meaning. The description mentions 'optionally filtered to one property' which maps to property_id, and 'all_pages=true' which maps to the all_pages parameter. However, it does not explain limit, offset, fields, or exclude_fixtures, leaving those to the schema's names and defaults. The description adds some value but does not fully compensate for the 0% coverage.

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 states a specific verb and resource ('List rental units') and notes an optional filter to one property, which distinguishes it from sibling tools like buildium_list_tenants or buildium_list_rentals. It does not explicitly name a sibling alternative, but the resource and filter scope are clear enough for an agent to select it.

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 gives clear context for when to use the tool: listing rental units, optionally filtered by property. It also provides a specific usage directive: set all_pages=true when counting or aggregating, because one page is not the whole collection. It does not explicitly state when not to use it or name alternatives, but the guidance is actionable and context-rich.

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