get_subtasks

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

With no annotations, the description carries full burden for behavioral transparency, but it only states the basic action. It does not disclose whether subtasks are returned recursively, pagination behavior, performance implications, or any side effects. The agent gains no insight beyond the minimal 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 extremely concise—a single sentence that immediately conveys the tool's purpose. No extraneous words or fluff. It is front-loaded and efficient.

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 that there is no output schema, the description should ideally hint at the return format or structure, but it does not. For a simple list tool with 100% parameter documentation, the description is minimally adequate but lacks details about the response (e.g., whether it's a flat list or includes nested subtasks).

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 100% (all parameters have descriptions), so baseline is 3. The tool description adds no additional meaning beyond what the schema already provides for parameters like task_id, custom_task_ids, and team_id.

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 'Get the subtasks of a task' clearly states the verb ('Get'), resource ('subtasks'), and context ('of a task'). It distinguishes from sibling tools like get_task (which returns a single task) and get_tasks (which returns a list of tasks) by specifying subtasks.

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?

No guidance is provided on when to use this tool versus alternatives like get_task or get_tasks. There is no mention of when not to use it, no usage context, and no comparison to other tools.

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