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

The readOnlyHint annotation already declares this as a safe read operation. The description adds useful context beyond that by naming the returned fields (title, status, priority, due date, vendor, amount, line items, linked task and bill ids) and the available filter dimensions, plus the underlying endpoint. It does not mention pagination behavior or rate limits, but with annotations covering safety, this is a strong addition.

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?

The description is two sentences plus an endpoint reference, front-loading the core purpose before enumerating returned fields and filters. It is efficient with no filler, though the endpoint line is somewhat meta and could be omitted without losing agent-relevant meaning.

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?

Given a rich schema with 100% description coverage, readOnly annotations, and no output schema, the description is largely complete: it explains what the tool does, what it returns, and what can be filtered. The main gap is the absence of pagination guidance, though the schema's limit and offset parameters mitigate this.

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 22 parameters are fully documented in the schema itself. The description lists many of the filterable fields, which adds marginal grouping value, but it omits several parameters (orderby, limit, offset, task_ids, task_category_id, unit_agreement_id) and provides no syntax beyond what the schema already gives. Baseline 3 applies when the schema does the heavy lifting.

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 work orders') and enumerates returned fields and filter dimensions, making the tool's function clear. However, it does not distinguish itself from siblings like buildium_get_work_order or buildium_list_tasks, so an agent must infer the distinction from the name alone.

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 lists filter capabilities but provides no explicit guidance on when to use this tool versus alternatives such as get_work_order or list_tasks. It does not state prerequisites, exclusions, or the conditions under which a filtered list is preferable to a single-record fetch.

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