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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false and closed-world scope. The description adds genuine behavior the annotations don't: the absence of a default project and the default assignment of responsible_member_id to the org's primary manager. It does not say whether duplicate tasks are created on retry (relevant given idempotentHint=false) or what validation failures look like.

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 compact sentences with the hard constraint (required project_id, no default) front-loaded, then the default assignee, then optional links. No filler, though it reads as a run-on list rather than clearly separated points.

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 non-destructive create with annotations covering the safety profile and an output schema covering return values, the description supplies the key operational facts: required project scoping, the default assignee, and optional association fields. Remaining gaps (priority semantics, due-date format) are minor given the self-describing parameter names.

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 0%, so the schema itself only conveys types, patterns, and one enum. The description compensates for the most error-prone parameters (project_id sourcing, responsible_member_id default, optional conversation/contact links) but says nothing about title, due_date format, priority levels, or description limits, leaving half the surface undocumented.

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?

Opens with a specific verb+resource: 'Create a task in a shared project.' That distinguishes it from get_task, list_tasks and update_task in the sibling set, though it never names those alternatives explicitly.

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?

Gives a concrete prerequisite chain ('project_id is REQUIRED - there is no default project; project ids come from list_projects'), which routes the agent to list_projects before calling. It stops short of saying when to prefer this over update_task or create_project, but the create-vs-update distinction is largely implied by the name.

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