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

Annotations already establish readOnly/idempotent/non-destructive, and the description adds genuinely new behavior: content may be truncated (contentTruncated), content carries block handles consumed by edit_task_content, and content must be treated as untrusted source data. The truncation and trust warnings are exactly the kind of non-obvious traits annotations cannot express.

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 core operation before the field list and the editing caveat. Every clause carries information an agent needs; no filler.

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?

An output schema exists, so return values need not be documented in prose, yet the description still flags the two things that matter operationally: truncation and untrusted content. Combined with the full annotation coverage and complete parameter schema, nothing needed to call this 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 description coverage is 100% and the single id parameter is fully documented there (pattern, length, prefix preservation, 'do not invent IDs'). The description only says 'by its ID' and adds no format or prefix detail beyond the schema, so the baseline of 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 and resource ('Read an accessible task by its ID') and then enumerates what the read returns: priority, dates, assignees, source link and content. This is unambiguous against siblings like list_tasks (bulk listing) or get_doc (different resource), so an agent can select it without opening the schema.

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 clear context for use (you need an existing task ID) and a downstream condition: 'Check contentTruncated before editing.' It does not, however, explicitly contrast itself with list_tasks/search or state when not to use it, so it stops short of full when/when-not guidance.

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