karea_list_subtasks

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

No annotations provided, so the description must disclose behavior. It mentions parameter flexibility but does not state whether the operation is read-only, if it modifies anything, or any constraints. Lack of behavioral details (e.g., paging, sorting, return format) leaves the agent uncertain.

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?

Single sentence, front-loaded with the primary action, no extraneous words. Every word conveys essential information.

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?

Lacks details on output (e.g., format of listed subtasks), prerequisites (e.g., parent must exist), and any potential side effects. For a tool with no output schema, more context is needed to fully prepare the agent.

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?

The input schema already describes both parameters. The tool description adds minimal context ('Accepts the parent by visual ID, name, or UUID') which is already in the schema. With 100% schema coverage, baseline is 3 and no extra value is added.

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 action (list subtasks) and the target (parent task), and specifies acceptable input types (visual ID, name, UUID). It distinguishes from sibling tools like karea_list_tasks which lists all tasks.

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 implies usage context (when you need subtasks of a specific parent), but does not explicitly state when not to use it or compare with alternatives like karea_list_tasks or karea_create_subtask.

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