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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered by structured data. The description adds only that the result is the complete set of comments ('all'), without mentioning ordering, pagination, or whether deleted comments are included.

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, front-loaded with the purpose before the parameter callout. The second sentence is largely redundant with the schema's required array, which keeps it from a 5.

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 simple filtered-list read tool with rich annotations and fully documented params, this is close to sufficient, but with no output schema the agent cannot learn the shape of a returned comment (author, timestamps, pagination), and the description does not fill that gap.

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%: board_id ('Board ID where the task belongs') and task_number ('Task number in board scope') are already documented. The description merely repeats that both must be provided, adding no format, scoping, or validation detail beyond the schema.

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 ('retrieve all comments') plus the scope ('for a specific task'), so an agent can instantly tell it apart from add_comment or delete_comment in the sibling list. It stops short of explicitly naming the write siblings it is not, which keeps it from a 5.

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?

'Use this to retrieve all comments' implies the usage context, and it names the two required inputs. There is no explicit statement of when to prefer it over list_task_activity or search_tasks, and no exclusions, so guidance remains implied rather than spelled out.

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