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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds two pieces of genuine behavioral context beyond the annotations: the required UNITS read permission and the fact that results are single-page with a 'next' cursor that preserves filters. It does not describe return shape or default paging size, keeping it from a 5.

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 purpose, then pagination and the permission prerequisite. No wasted words.

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 10-parameter read tool with 20% schema coverage and no output schema, the description leaves the majority of filter semantics undocumented. An agent can call it, but cannot confidently use most parameters.

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 only 20% (just the two ID fields), so the description must compensate; instead it is silent on limit, offset, vacant, orderby, publishedForRent, includeDeactivated, and the lastModifiedDateTime range. 'One page' hints at pagination but gives no limit/offset semantics.

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 (Propertyware units), distinguishably different from the sibling propertyware_get_unit for single-record retrieval. Clear, but it doesn't explicitly name the sibling or scope beyond 'units'.

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?

Provides real guidance on pagination: 'One page; use next (preserves filters) for the following call.' However, it never says when to use this list tool versus get_unit, nor when the various filters (vacant, publishedForRent, includeDeactivated) are appropriate.

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