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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description goes beyond that by disclosing that this returns a deep, fully-hydrated record including nested collections (checklists with items, comments with reactions), which tells the agent to expect a heavy read rather than a shallow one.

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 sentence with the core purpose front-loaded, followed by a field inventory that is long but each item earns its place as a scoping hint. No filler, no restatement of the title.

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 carries the return-value burden and does so thoroughly by enumerating the assembled parts. The remaining shortfall is parameter coverage for cardId. For a read-only, single-resource fetch this is largely complete.

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 50%: the 'include' enum is documented in the schema itself, but 'cardId' has no description anywhere. The description says only 'one task' and never clarifies that cardId is the task identifier. With half the parameters undocumented, the description fails to compensate for the coverage gap.

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 ('Reads one task in full') and then enumerates the exact payload surface — title, description, labels, assignees, checklists, comments, custom fields, watch state, reminders. This distinguishes it from single-resource siblings like get_board and from list-oriented tools like list_my_tasks or search_tasks without opening any 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?

Usage is only implied: the singular 'one task' suggests it is for fetching a known task by id rather than browsing. There is no explicit when-to-use statement, no mention of alternatives such as search_tasks or list_my_tasks, and no prerequisite or exclusion guidance.

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