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

readOnlyHint=true already tells the agent this is a safe read, so the description's real contribution is the disclosure that the vendor does not paginate this endpoint — genuinely useful behavior that prevents pointless page-looping. What it omits is anything about ordering, size, or what an empty result looks like.

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 tight sentences with no filler. The purpose statement comes first and the pagination caveat second, which is exactly the right front-loading for a tool this simple.

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 single-parameter list tool with full schema coverage and readOnlyHint, almost everything an agent needs is present, and the no-pagination note closes the main operational gap. The only missing piece is a hint at the return shape (author, timestamp, body fields), which matters slightly more here because no output schema exists.

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 coverage is 100% and the single `id` parameter is fully documented in the schema, including the numeric-string precision rationale. The description only reinforces that the id refers to a building; it adds no format or constraint detail beyond the schema, 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?

The description gives a specific verb and resource ("Read notes") scoped to "one Propertyware building," which is enough to separate it from broader list tools like propertyware_list_buildings and from the related propertyware_list_lease_notes. It stops short of naming a sibling explicitly, so it lands just below the top mark.

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 scoping phrase "for one Propertyware building" implies this is the per-building notes lookup rather than a bulk listing, but there is no explicit statement of when to choose this over propertyware_get_building (which may also surface notes) or how it relates to propertyware_list_lease_notes. Usage is inferable rather than stated.

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