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

Annotations only carry destructiveHint=true, so the description has to carry the rest. It discloses that the task is internal, must be assigned to a staff user, and may be linked to property/unit/category with a due date — useful scoping. It says nothing about required permissions, whether the created task is returned, or what happens on failure, so it only partly compensates for the thin annotation set.

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?

A single front-loaded sentence carrying the core meaning, followed by a short endpoint reference. No redundant or filler text.

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?

No output schema exists, so an agent has no idea what the call returns (e.g. a task id), which matters for chaining into buildium_update_todo_task. For a 10-parameter creation tool with only a destructiveHint annotation, the description also omits permission requirements and error behavior.

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 10 parameters are already documented in the schema, including the cross-field constraint that unit_id must belong to property_id and the enum values for status and priority. The description only restates a subset of that (assignee, property/unit, category, due date) without adding format or constraint detail, 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?

States a specific verb and resource ('Create an internal to-do task') plus scope (assigned to a staff user, optionally tied to a property/unit and category, with a due date) and the backing endpoint POST /v1/tasks/todorequests. The word 'internal' and 'to-do task' distinguish it from the sibling buildium_create_work_order.

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?

Usage is implied by 'internal to-do task' versus the work-order sibling, and by the optional property/unit linkage, but the description never says when to choose this over buildium_create_work_order, buildium_update_todo_task, or buildium_list_tasks. No prerequisites are stated.

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