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

With destructiveHint=true already declared, the description still adds value: it discloses the exact endpoint (POST /api/v0/tasks), the form-encoded body convention, and the response envelope { meta, response }. It does not cover auth requirements or any post-write side effects, so not a 5.

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 tight sentences, mutation warning and parent-object constraint front-loaded, with the API detail trailing. No filler and nothing repeated from the schema or annotations.

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 create tool with no output schema, the description covers the mutation nature, the endpoint, the attachment requirement, and the return shape. Nothing an agent needs to invoke it correctly is missing.

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 3 is the floor, but the description goes further by explaining the semantic rationale for against_type/against_id (a task is always attached to a parent object) and by noting that the 'fields' bag is merged into the form-encoded write body — meaning beyond the schema text.

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 gives a specific verb and resource ('MUTATES Accelo data: creates a new task') and immediately scopes it as a child-object creation ('always logged AGAINST an object'), which separates it from the flat entity creators like create_company or create_contact in the sibling list.

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 states a real usage prerequisite — that against_type and against_id are mandatory because tasks must attach to a parent object — but never says when to pick create_task over create_activity or the get_/list_task tools. Prerequisite coverage is good; alternative-selection guidance is absent.

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