Buildium List Rentals

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

The annotations already mark the tool as read-only, idempotent, and non-destructive, so the description's main behavioral contribution is pagination context: a single page is limited to the first 50 records, and `all_pages=true` follows pagination to the end. It also warns about the incorrectness of counts taken from a single page, which is valuable behavioral detail beyond the annotations.

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 short, front-loaded with the core purpose, and every sentence earns its place. The pagination warning is dense but highly relevant, and there is no filler or repetition of annotation values.

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?

The output schema exists and the annotations cover the read-only/idempotent safety profile, so the description does not need to explain return values or mutation risks. However, with five optional parameters and zero schema descriptions, the lack of any explanation for `exclude_fixtures` leaves a notable gap in the information needed to use the tool fully.

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 bears the burden of explaining parameters, but it only covers `fields` and `all_pages`. `limit`, `offset`, and particularly `exclude_fixtures` receive no semantic explanation, leaving an agent without enough context to confidently set those parameters.

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 opens with a clear verb and resource, 'List rental properties,' which unambiguously states the tool's core purpose. It does not explicitly differentiate from sibling tools like list_units or list_leases, but the resource noun 'rental properties' is distinct enough to avoid significant confusion.

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 concrete, actionable guidance: pass `fields` to narrow large records and set `all_pages=true` when counting or aggregating, explaining that a single page is only the first 50 records. It does not mention when to choose this tool over named alternatives, but it clearly explains when the pagination option should be used versus avoided.

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