get_subtasks

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

With no annotations, the description carries the full behavioral burden. 'Get' implies a read, but it says nothing about whether results are paginated, ordered, nested recursively (do subtasks have their own subtasks?), or what permissions/board access are required. For a zero-annotation tool this is a substantial gap.

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 short sentence with no filler and the resource scoping front-loaded. It is efficiently sized, though so terse that the brevity reflects under-specification rather than tight editing.

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 two-parameter read tool with no output schema, the description is minimally viable: the agent knows it returns subtasks. However, it omits the meaning of task_id and any hint about the return shape (flat list vs. nested tree), which matters for a hierarchy-related call.

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 50%: board_name is documented in the schema (including a pointer to list_boards), but task_id has no description anywhere. The description adds no parameter meaning at all, so it fails to compensate for the undocumented required task_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?

States a specific verb ('Get') and resource ('subtasks') scoped to a single task, so an agent immediately knows it retrieves child tasks of one parent. It does not differentiate itself from nearby siblings such as get_task or create_subtask, but the purpose itself is unambiguous.

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 gives no when-to-use context, no prerequisites, and no mention of alternatives (e.g. get_task, create_subtask, or how to get top-level tasks). The agent must infer that this is the read path for a task's children purely from the name.

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