Buildium List Leases

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

Annotations already indicate read-only, idempotent, and non-destructive behavior. The description adds useful behavioral context beyond those annotations, such as rent terms being included in AccountDetails and the pagination intent behind all_pages=true. No contradiction with 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 main purpose is front-loaded, and every subsequent sentence earns its place by either clarifying row contents, routing to a sibling tool, or giving pagination guidance. There is no filler or repetition.

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 covers return values and annotations cover the safety profile, so the description doesn't need to restate those. It covers status values, row contents, pagination intent, and sibling routing well; the only minor gap is the lack of explanation for exclude_fixtures and fields.

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. It explains lease_status values and clarifies all_pages usage, but leaves property_id, exclude_fixtures, fields, limit, and offset without added meaning. This is partial compensation rather than full 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?

States the exact operation and resource: 'List leases.' It also names the lease_status filter values (Active, Future, Past, Expired) and clarifies what each row contains, so an agent can distinguish this from get_lease, list_lease_transactions, and lease_roster.

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?

Provides explicit routing guidance: buildium_list_lease_transactions is for posted charges/payments, buildium_lease_roster is for occupants, and all_pages=true is recommended when counting or aggregating. This is exactly the when-to-use vs alternative information an agent needs.

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