Buildium Get Rental

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

Annotations already report read-only, idempotent, and non-destructive behavior, so the description does not need to repeat them. The main text adds no behavioral detail; only the schema's fields description notes that Buildium records can be large and carry sensitive fields, which is modest additional context. No contradiction with 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?

A single front-loaded sentence with no filler. It conveys the essential operation and selection criterion immediately, and every word 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 simple one-by-ID read tool, the description, together with the fully described parameters, output schema, and read-only/idempotent annotations, gives an agent everything needed to call it correctly. The only optional improvement would be explicit sibling routing, but this is not required for correctness.

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 the schema already documents rental_id and fields. The description's 'by ID' only reinforces rental_id and adds no meaning beyond the schema; the helpful fields guidance lives in the schema, not the tool description, so baseline 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?

The description states a specific action ('Get'), a precise resource ('one rental property'), and the selection criterion ('by ID'). It distinguishes itself from sibling buildium_list_rentals by emphasizing a single record lookup, so an agent can select it without opening the schema.

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 phrase 'one rental property by ID' establishes clear context: use this when the agent has a rental_id and needs a single entity. It does not explicitly name alternatives or exclusions (e.g., buildium_list_rentals for multiple properties), so it stops short of full explicit guidance.

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