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

Annotations already declare readOnlyHint=true, so safety is covered. The description adds the BUILDINGS read permission requirement and clarifies pagination behavior ('next preserves filters'), which is useful context beyond the annotations. It does not cover rate limits or error behavior, but those are less critical for a read-only list tool.

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 the core action and followed by pagination and permission notes. Every sentence adds value with no wasted text.

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-parameter filtered list operation with very low schema description coverage and no output schema, the description is incomplete. It covers pagination and permissions but omits nearly all parameter meanings and does not describe what the returned page contains.

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?

There are 11 parameters with only 9% schema description coverage. The description mentions 'filters' generically but does not explain the meaning of name, limit, offset, vacant, address, orderby, category, portfolioID, publishedForRent, or the date range parameters. This leaves most parameter semantics undocumented.

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 states a specific verb and resource: 'List Propertyware buildings.' This clearly distinguishes it from the sibling 'get_building' by implying a collection query, though it does not explicitly name alternative tools.

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?

It provides pagination guidance ('One page; use next...') and a permission prerequisite, but does not explain when to use this tool versus 'get_building', 'list_units', or other list siblings, nor does it give exclusion criteria.

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