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

Annotations declare readOnlyHint=false and destructiveHint=true, yet the description says only that a task is 'added' — it never addresses why the operation is flagged destructive (does it consume or alter the template? is it reversible?) or what permissions are needed. With annotations doing the safety signaling, the description should have explained this tension, and instead adds nothing.

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?

A single well-formed sentence with no filler; the action and source are front-loaded. It is appropriately sized, though the brevity is partly under-specification rather than disciplined concision.

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 write tool with no output schema, no annotation commentary, and 0% parameter documentation, the description leaves key gaps: required permissions, destructive behavior rationale, and parameter formats. An agent could invoke it, but without real confidence about side effects.

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 description must carry the burden, but it only loosely maps the two parameters to concepts ('a list', 'one of the board's card templates'). It gives no format guidance (ID vs name, where to obtain listId/templateId), leaving the agent to guess at values.

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 (adds) and resource (a task to a list), and names the source (card template), which implicitly separates it from the plain create_task sibling. It never names an alternative explicitly, so differentiation is inferable rather than stated.

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, when-not-to-use, or alternative is given, despite several closely related siblings (create_task, save_task_as_template, duplicate_task). The only guidance is the implied precondition that a card template on the board exists.

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