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

readOnlyHint=true already tells the agent this is a safe, non-mutating read, so the description needn't restate safety. It adds concrete value by naming the returned shape (contact details, agreement dates, owned property ids), but says nothing about pagination defaults, result volume, or auth requirements beyond what the schema implies.

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?

Two tightly written sentences with zero filler; the resource definition and return contents are front-loaded and the API endpoint trails as a compact reference.

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 read-only list endpoint with no output schema and fully documented parameters, the description covers purpose, scope, and the salient returned fields, which is nearly all an agent needs. It stops short of noting that all parameters are optional and that results are paged, which would have completed the picture.

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 every one of the ten filters (limit, offset, status, orderby, date ranges, phone, owner_name, property_ids) is already documented with format and defaults. The description adds no filter-specific syntax or semantics, so the baseline 3 applies.

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 a specific verb and resource ('List rental owners') and immediately disambiguates the domain term with a parenthetical ('the landlords you manage for'). It also names the returned fields, so an agent can distinguish it from buildium_list_tenants or buildium_list_vendors 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?

There is no guidance on when to use this tool versus siblings, nor any mention of the filtering scenarios its ten optional parameters enable. The only routing signal is the resource noun itself, which the agent must infer.

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