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

Annotations provide only destructiveHint=true, so the description carries most of the behavioral burden. It confirms the write via the POST /v1/tasks/todorequests endpoint, but says nothing about permission requirements, what the caller gets back, or any side effects of assignment.

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 compact sentences, with the core purpose front-loaded before the endpoint reference. The trailing API path adds little an agent needs but wastes very little space.

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 10-parameter creation tool with no output schema and minimal annotations, the description covers the what but omits return shape, permission scope, and validation behavior (e.g., unit/property coupling). Adequate but with clear gaps.

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 every parameter is already documented and the baseline is 3. The description adds only the optionality groupings (property/unit/category/due date as optional) but does not explain the required vs optional split or the unit-must-belong-to-property constraint already in the schema.

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') and qualifies it as staff-assigned with optional property/unit/category ties. The 'internal' framing distinguishes it from buildium_create_work_order, which is the main adjacent sibling.

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 implies a context (internal staff task) but never states when to choose this over buildium_create_work_order or how to route between them. No exclusions or prerequisites are given, so usage must be inferred from the sibling list.

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