stories-add-subtask

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

Without any annotations, the description must convey behavioral traits. It only states the action but does not disclose side effects (e.g., whether the subtask is reassigned from a previous parent, or if any data is modified). This is insufficient for safe usage.

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 a single sentence with no unnecessary words. 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?

The tool modifies data (adds a subtask relationship) but lacks any description of return values, error conditions, or behavioral constraints. Given no output schema and no annotations, the description is incomplete for safe and effective use.

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 has 100% description coverage, with both parameters described as 'Parent story ID' and 'Sub-task story ID'. The description adds no additional meaning beyond the schema, achieving the baseline score.

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 'Add existing story as a sub-task' clearly states the action (add) and the resource (existing story as sub-task), and it differentiates from siblings like 'stories-create-subtask' (which creates a new story) and 'stories-add-task' (which adds a task, not a sub-task).

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 'stories-create-subtask' or 'stories-add-task'. The description does not mention prerequisites, exclusions, or context for use.

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