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

Annotations already declare readOnlyHint=true, and the description reinforces it ('Read-only') without contradicting. It adds genuinely useful context beyond the annotation by naming the underlying endpoint (Buildium: GET /v1/bills) and enumerating what the response contains, though it says nothing about paging defaults or rate limits.

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 short sentences, front-loaded with the resource and scope, then the endpoint reference. Every clause earns its place and nothing is padded.

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 an 11-param read-only list tool with no output schema, the description covers purpose, scope, read-only nature, and the returned field set, which compensates for the absent output schema. It is slightly thin on pagination/filtering behavior, but the schema carries those details.

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 all 11 params (limit, offset, orderby, entity_id/vendor_id/entity_type, paid_status/dates, reference_number, approval_statuses) are already fully documented in the schema. The description adds no parameter-level syntax or format detail, 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 ('List') and resource ('vendor bills (accounts payable)'), and enumerates the fields returned (dates, memo, vendor, work order, reference number, approval status, lines). An agent can distinguish it from the other list_* siblings by resource alone without opening any 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?

Usage is implied by the read/list framing plus the filter parameters, but there is no explicit when-to-use statement, no when-not-to-use, and no routing to alternatives such as buildium_list_lease_transactions or buildium_list_outstanding_balances for related AP questions.

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