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

Discloses permission prerequisites and an error condition (foreign/missing id -> 404). Since no annotations are provided, the description carries the burden; it gives meaningful behavioral context but does not mention success response or other potential errors.

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?

Three short, focused sentences with no unnecessary details. Each sentence adds value: what it does, what permission is needed, and a key error response.

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?

Covers the core behavior, permission, and a common error. It lacks details about success response shape or other error codes, but for a simple delete operation this is arguably sufficient.

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?

The description only vaguely references 'foreign or missing id' without clarifying which parameter it refers to or how organization_id and task_id relate. The schema provides no additional description beyond names, so parameter semantics are poorly explained.

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?

Clearly states 'Deletes one task from the tenant CRM.' The verb 'delete' and noun 'task' make the operation unambiguous, and it is distinct from sibling create/get/list/update operations.

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?

Provides usage-relevant information: requires 'crm:write' permission and indicates that a foreign or missing id results in a 404. It doesn't explicitly name alternatives, but the delete verb makes the intended use clear.

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