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

Annotations already declare destructive=true, idempotent=false and openWorld=true; the description adds real value on top by disclosing the misleading boolean return ("request accepted", not "actually pushed") and the auth/scope requirement. It stops short of warning that re-invoking creates duplicates despite non-idempotency, which is the main operational risk.

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 sentences, front-loaded with the action, then preconditions, then the return caveat. Slightly weakened by making the key caveat a cross-reference that only makes sense if the Jira tool's description was read.

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?

With no output schema, the description partially compensates by characterizing the response as a boolean acceptance. But for a destructive, non-idempotent push it omits duplicate-creation behavior on retry and what fields/tasks get transferred, leaving meaningful gaps for the calling agent.

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%, including nested-location hints (`hub_get_call.call.callUuid`) and account/workspace semantics, so the schema carries the parameter burden. The description adds nothing parameter-specific — notably it does not say how to obtain a valid `selectedListId` (e.g., via list_spaces/list_boards).

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 and resource ('Push a call's extracted tasks into a ClickUp list') and implicitly distinguishes itself from the sibling send targets (Airtable, Jira) by naming the destination. The explicit reference to `hub_send_call_to_jira` further anchors it within its tool family.

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 concrete preconditions — requires `recordings:write` scope and a ClickUp integration on the workspace — which is more than most siblings offer. It does not, however, state when to prefer this over the Airtable/Jira variants or what to do if the integration is missing.

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