list_rental_tenants

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

With no annotations, the description carries full responsibility for behavioral disclosure. It only says 'List' which implies read-only, but it omits pagination behavior, default limit/offset, and whether it returns unfiltered data. No side effects or data scope are disclosed.

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 a single concise sentence with no wasted words, but it under-specifies the tool's capabilities. It is efficient but not sufficiently informative for an agent to use correctly.

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 tool has five optional parameters and sits among many related list tools. The description fails to explain filtering options, typical use cases, or alternatives, leaving significant gaps in context. An output schema exists, so return values are covered, but other contextual aspects are missing.

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?

The schema has 0% parameter description coverage, and the description provides no explanation for limit, offset, status, unit_id, or property_id. The agent cannot infer what these filters mean or how to use them.

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 clearly identifies a specific verb ('List') and resource ('rental tenants') from Buildium, distinguishing it from siblings like list_rentals and list_association_tenants. It is unambiguous but lacks any detail about the scope or what constitutes a rental tenant.

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?

No usage guidance is provided. It does not mention when to choose this tool over alternatives such as list_rentals or list_association_tenants, nor does it hint at filtering by property or unit.

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