list_subtasks

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

Annotations declare readOnlyHint=true, so description's behavioral addition is limited to cost (same as get_task) and the lack of a dedicated endpoint. No mention of error cases or pagination, but acceptable for a simple read operation.

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?

Extremely concise: two sentences plus a brief cost note. Purpose is front-loaded in the first sentence. No wasted words.

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?

Covers purpose, usage context, and API limitation. Relies on output schema for return values. Missing potential details like ordering of subtasks, but overall complete for a straightforward list tool.

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?

Only parameter is task_id, which is self-explanatory. Description implies its role ('on a task') but adds no detail beyond the schema (type integer, minimum 1). With 0% schema coverage, baseline is low; the obviousness of the parameter prevents a lower score.

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?

Description clearly states the verb 'list' and the resource 'subtasks on a task', listing specific fields returned. It distinguishes from sibling tools like add_subtask, update_subtask, delete_subtask, and reorder_subtasks by focus on listing.

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?

Indicates when to use ('sugar for callers that only want the list') and notes the alternative of fetching the full task via get_task. Cost comparison (one HTTP call) adds practical guidance, though explicit 'when not to use' is absent.

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