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

Annotations already declare readOnlyHint=true, so the safe-read profile is covered. The description adds the returned field set (category, property, unit, requester, assignee, status, priority, due date) and the underlying endpoint, but says nothing about pagination behavior, result caps, or how filters combine — meaningful context it could have supplied.

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?

Front-loaded with the core verb and resource, then the returned field set, then the endpoint line. Dense but every clause carries signal, especially the field enumeration given there is no output schema.

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 17-parameter, zero-required list endpoint with no output schema, the description covers scope and returned fields but omits paging defaults, maximum result expectations, sort behavior, and the entity_type/entity_id dependency. Adequate but with clear gaps.

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%, with all 17 parameters individually documented (limits, date formats, enum values, entity_type/entity_id coupling), so the schema does the heavy lifting. The description's field list refers to returned fields, not parameters, and adds no filter semantics beyond the schema.

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 and resource ('List all tasks/requests') and enumerates the four concrete subtypes it returns, which maps directly to the type enum. It does not, however, explicitly contrast itself with buildium_list_work_orders, the closest sibling, so differentiation is left to inference.

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 description says what the tool returns but never states when to choose it over buildium_list_work_orders or the get_* siblings, nor any prerequisites or exclusions. An agent gets no routing guidance beyond the resource name.

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