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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds that the new item sits under a task, but says nothing about permission requirements, whether the parent task is modified, ordering of inserted items, or limits on subtask count.

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 clear sentence, front-loaded with the action and the clarifying parenthetical, with no filler. It is efficient, though arguably terse given the undocumented parameters.

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 tool with annotations covering safety and no output schema, the description gives the minimum needed to understand intent. It falls short on parameter meaning and on distinguishing this tool from add_task, which are the remaining gaps an agent would need filled.

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 0% with two required parameters. The phrase 'under a task' weakly implies task_id identifies the parent task, but neither task_id's expected format nor title's constraints (1-200 chars) are conveyed in the description, so it does not compensate for the schema gap.

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?

Specific verb (add) plus resource (subtask) with a helpful gloss that 'subtask' means a checklist item, and 'under a task' states the containment relationship with the parent task. It is distinguishable from the sibling add_task, though it doesn't explicitly say how it differs.

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?

Usage is only implied: the tool is for creating checklist items beneath an existing task, which suggests a task must already exist. It never states when to use this instead of add_task, nor any prerequisites or exclusions, leaving the sibling routing ambiguous.

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