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

Annotations already declare readOnlyHint=true, so the safety profile is covered and the description only needs to add extra context. It discloses the underlying endpoint (GET /v1/tasks) but says nothing about result volume, pagination defaults, or permission scoping beyond what the schema already encodes.

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?

One compact sentence front-loads the resource and its subtypes, followed by a short endpoint reference. Efficient, though the Buildium endpoint notation is marginally redundant for an agent that already has the tool name.

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 but zero-required, read-only list tool with a fully documented schema and no output schema, the description covers purpose and scope adequately. It would be stronger if it hinted at default paging behavior, but nothing essential to invoking it is missing.

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%, so all 17 parameters are already documented with types, bounds and enums. The description's field list (category, property, unit, requester, assignee, status, priority, due date) loosely maps to filterable params but adds no syntax or semantics 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?

Specific verb (List) plus resource (tasks/requests), with an explicit enumeration of the four subtypes it covers (contact, resident, rental owner, to-do) and the fields returned. An agent can distinguish it from buildium_list_work_orders or buildium_list_tenants without opening the 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?

The description states what the tool does but gives no guidance on when to choose it over siblings such as buildium_list_work_orders, nor any prerequisite or exclusion. Usage is only implied by the resource name.

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