Buildium Get Rental

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 fully covered. The description adds no behavioral context beyond the schema, such as return format or error behavior, but with strong annotations the bar is lower. 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 sentence with zero waste. The essential information (get one rental by ID) is front-loaded and complete. Nothing extraneous.

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 read-by-ID tool with strong annotations and an output schema, the description is nearly complete. The only minor gap is not explaining the optional 'fields' parameter's behavior (e.g., projection), but the parameter name and output schema likely cover that. The tool is simple enough that this description suffices.

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 carries the burden for parameter meaning. However, the description's 'by ID' directly maps to the required rental_id parameter, and the optional fields parameter is self-explanatory as a field selector. The description adds minimal value beyond the schema, but the parameter names are clear enough.

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 'Get one rental property by ID' clearly states the verb (get), resource (rental property), and scope (one by ID). It distinguishes from siblings like buildium_list_rentals (which lists multiple) and buildium_get_lease (different resource), though it doesn't explicitly name them.

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 implies usage: use when you need a single rental property by ID, not a list. It doesn't explicitly state when not to use it or name alternatives, but the 'by ID' qualifier and sibling names provide enough context for an agent to infer the right choice.

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