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

The readOnlyHint annotation already declares this a safe read, so the bar is lower. The description adds the upstream API mapping (GET /v1/workorders) and confirms the shape of returned data, which is useful context, but it says nothing about pagination defaults, result caps, or ordering behavior 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?

Two sentences, both front-loaded: returned fields first, then filterable dimensions, then endpoint. No filler. Slightly dense but every clause carries information.

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?

With 22 optional params and no output schema, the description usefully previews the returned fields and all filter families so an agent can plan a query without opening the schema. The main omission is pagination/result-cap behavior, though limit and offset are documented in the schema.

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 22 documented parameters, so the schema carries the semantic burden and baseline is 3. The description groups the filter families into a readable list but adds no syntax, format, or combination rules beyond that grouping.

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 (work orders), enumerates the fields returned (title, status, priority, due date, vendor, amount, line items, linked task/bill ids), and names the underlying endpoint. This clearly distinguishes it from buildium_get_work_order (single fetch) and buildium_list_tasks.

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 enumerates the filter dimensions available (entity, status, priority, task type, unit, vendor, assignee, dates, amount, billed flag, title), implying this is the query tool for work orders. However, it never states when to prefer it over buildium_get_work_order or how it relates to buildium_list_tasks/list_bills, so usage is inferred rather than guided.

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