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

Annotations already declare readOnlyHint=true, and the description restates 'Read-only', which is consistent rather than contradictory. It adds the backing endpoint (GET /v1/bills) but no pagination behavior, result caps, or rate-limit context beyond what the schema's limit/offset already convey. With annotations carrying the safety profile, this is adequate but not rich.

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?

Three short sentences, front-loaded with what is returned before the read-only note and endpoint. Very little waste, though 'Read-only' mildly duplicates the annotation and the endpoint reference is optional metadata for an agent that never calls the raw API.

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?

With 11 optional parameters, no output schema, and no nested objects, the description usefully compensates by enumerating the shape of returned bills. Pagination and filtering semantics live in the schema, so nothing critical is missing, but it stops short of describing paging defaults or result ordering behavior.

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% across all 11 parameters (limit, offset, orderby, entity_id/entity_type, paid_status, paid dates, reference_number, approval_statuses), so the schema does the heavy lifting. The description adds no parameter-level detail (e.g. that entity_type is required alongside entity_id) beyond the schema text. Baseline 3 is correct.

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?

Specific verb+resource ('List vendor bills (accounts payable)') with a parenthetical clarifying the domain, plus an enumeration of the returned fields (dates, memo, vendor, work order, reference number, approval status, lines). It also names the backing endpoint, so an agent can distinguish it from the other list_* siblings (leases, vendors, work orders) 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 resource (fetch AP bills), but there is no explicit when-to-use vs. alternatives, no mention of filtering strategies, and no note about when a different sibling (e.g. buildium_list_outstanding_balances) would be preferable. Minimum-viable context only.

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