list_subtasks

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

No annotations are provided, so the description carries the full burden. It indicates a read-only operation ('List all subtasks') but does not disclose potential behavioral details such as required permissions, return format, pagination, or behavior when no subtasks exist. It is not misleading, but adds only minimal transparency beyond the core action.

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?

The description is two sentences plus a useful example, with no wasted words. It is front-loaded with the core purpose and the example enhances usability. Every sentence earns its place.

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?

Given the tool's simplicity (one parameter, no output schema, no annotations), the description is nearly complete. It provides the core function, a related alternative, and an example. It could be improved by mentioning what is returned (e.g., a list of subtask objects) or handling edge cases, but for a simple listing tool, it is adequate.

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 schema already describes task_id as 'Parent task UUID'. The description adds an example ('Show subtasks of task <id>') and phrasing 'of a parent task', but this is largely redundant with the schema. It does not introduce additional semantic meaning beyond what the schema provides.

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?

The description clearly states the tool's function: 'List all subtasks of a parent task.' This uses a specific verb ('list'), resource ('subtasks'), and context ('of a parent task'), and the example further clarifies usage. It distinguishes from siblings like list_tasks (which likely lists top-level tasks) and create_task.

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?

The description provides a clear usage context: 'List all subtasks of a parent task.' It also mentions an alternative for a related operation: 'To create a subtask, call create_task with parent_task_id.' However, it does not explicitly state when not to use this tool (e.g., for top-level tasks) versus list_tasks, so it falls slightly short of explicit when-not guidance.

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