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

The description adds substantial behavior beyond annotations: omitted fields are preserved, null clears detail/dueAt, assignee reassignment may notify the new assignee, permissions are service-validated, and there is no persistent dedupe key. This aligns with destructiveHint and idempotentHint and provides important operational 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?

The description is compact but dense, with each sentence delivering operational guidance. It front-loads the login requirement and scope, then covers parameter semantics, sibling routing, and failure handling without repetition or fluff.

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 destructive, non-idempotent mutation with no output schema, the description covers prerequisites, permission nuances, field update semantics, alternative tool routing, timeout handling, and verification strategy. It is unusually complete.

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?

With only 20% schema coverage, the description compensates strongly: it explains that omission preserves values, null clears detail/dueAt, and assigneeId changes require assignment permission and may trigger notification. This directly clarifies the most ambiguous parameter behavior.

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 explicitly states the tool updates task title, description, due date, and assignee, and it names set_collaboration_task_status as the sibling for status changes. This gives a specific verb+resource and clearly differentiates from related tools.

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 provides explicit routing: status changes go to set_collaboration_task_status, and verification uses get_collaboration_goal. It also covers login requirements, permission checks, and post-timeout behavior with clear guidance not to auto-retry.

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