list_subtasks

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

No annotations provided, but description covers the return fields (id, title, status, user_id, time_estimated, time_spent) and implies a read-only operation. No side effects are mentioned, but this is acceptable for a list tool.

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?

Two sentences with no extraneous information. The action is front-loaded and clearly stated.

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?

Despite no output schema, the description fully documents the return structure. For a simple list tool with one parameter, this is complete.

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% with a description for task_id. The description does not add extra semantics for the parameter beyond 'ID of the task whose subtasks to list.' Baseline 3 is appropriate.

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 all subtasks') and the resource ('for a given Kanboard task'), with specifics on returned fields. It distinguishes from sibling tools like 'create_subtask' and 'update_subtask'.

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 when to use the tool (to list subtasks for a task) and requires a task_id. It does not explicitly state when not to use or compare to alternatives, but given the sibling list, the purpose is clear.

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