list_association_tenants

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only implies a read-only operation via 'List' but does not disclose pagination behavior (limit/offset), filtering options, rate limits, or any side effects. The existence of parameters hints at behavior, but the description itself adds minimal transparency.

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, which is easy to parse and front-loaded with the verb. However, it is under-specified for a tool with multiple parameters, sacrificing completeness for brevity. It is not verbose but lacks substantive content.

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 tool with four parameters, no annotations, and an output schema, the description is severely incomplete. It lacks any context about filtering, pagination, or when to use association tenants versus rental tenants. The agent would have to rely on the parameter names and output schema alone, which is insufficient for effective tool invocation.

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%, and the description does not mention any of the four parameters (limit, offset, status, property_id). It fails to compensate for the schema's lack of descriptions, leaving the agent without guidance on how to use these parameters or their meaning.

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 states the action ('List') and the specific resource ('association tenants'), distinguishing it from related tools like list_rental_tenants. The addition of 'from Buildium' provides source context. However, it offers no additional scope or detail beyond the tool's name, making it effective but not exceptional.

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 provides no guidance on when to use this tool versus alternatives such as list_rental_tenants or list_association_owners. There is no mention of typical use cases, prerequisites, or filtering scenarios, leaving the agent without context for selection.

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