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

The annotation only supplies destructiveHint=true, which the description is consistent with ('Create'). Beyond that, the description adds the required-parameter constraint (vendor_id, entry_allowed) and the API endpoint, but says nothing about permissions, idempotency, side effects, or what happens if both task and task_id are supplied. Useful but not rich behavioral context.

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?

It is a single dense paragraph that front-loads the purpose, then the task linkage options, then required fields, then optional line items, then the endpoint. Every clause carries information, though the run of parenthetical field lists is dense and could be slightly tighter.

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 12-parameter create tool with nested objects, no output schema, and only a destructiveHint annotation, the description covers the key decision points (task vs task_id, required fields, line items). It omits several scalar params (entry_notes, vendor_notes, work_details, chargeable_to, invoice_number, entry_contact_ids) and any return-value note, but schema coverage is 100% so those gaps are minor.

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 coverage is 100%, so the baseline is 3. The description goes beyond the schema by framing task_id and task as mutually alternative linkage mechanisms and by summarizing what the nested task object carries (title, priority, status, assigned staff, optional due date/property/unit) and that line items are optional with an optional GL account.

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 opens with a specific verb+resource ('Create a work order for a vendor') and immediately clarifies scope via the vendor requirement. It is trivially distinguishable from siblings like buildium_update_work_order, buildium_get_work_order, and buildium_create_todo_task.

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?

It gives clear selection guidance for the main branching decision — 'Attach it to an existing task (task_id) or create a new task with it (task)' — which is exactly the ambiguity an agent would hit. It stops short of naming alternative tools or stating when not to use this tool, so it falls short of a 5.

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