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

Annotations supply only destructiveHint=true, leaving the description to carry the rest, and it adds nothing beyond 'Create a new task' plus the REST verb. It discloses no auth/permission requirements, no side effects, no confirmation of what is created or what identifier comes back. The REST endpoint line is a mapping aid, not behavioral 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?

Two short sentences with the action front-loaded and zero filler. The 'Copper REST: POST /tasks' line is the one marginally expendable element, but it is cheap and helps API-aware agents.

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 nine-parameter creation tool with no output schema and only a destructiveHint annotation, the description is too thin: it omits the return value (e.g., the new task id), the required pairing of related_resource fields, and any defaults or constraints agents need before calling.

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 all nine parameters (name, tags, details, due_date, priority, assignee_id, reminder_date, related_resource_id/type) are already documented in the schema. The description adds no syntax, format, or interaction detail beyond that, so the baseline 3 applies.

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 ('Create') and resource ('task'), and the resource name alone distinguishes it from the sibling creators (company, lead, opportunity, person). It stops short of any explicit sibling differentiation or scope statement, but the purpose is unmistakable.

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?

No when-to-use guidance, no prerequisites, no alternatives named. It does not say when to create a task versus logging an activity, nor that attaching a task to a record requires the related_resource_type/id pair to be supplied together (only the schema hints at that).

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