Decompose feature

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

The description adds useful behavioral context beyond annotations: it confirms the destructive nature (deletes parent), explains the linking of subtasks, and states that new tickets are returned. Annotations already signal destructiveHint, but the description clarifies the exact behavior.

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 consists of two succinct sentences with no redundancy. The first sentence states the core action, and the second adds key details (creating linked subtasks, deleting parent, return value). Every sentence adds value.

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 description covers the main behavior (decomposition, deletion, return) but misses the keepParent parameter (optional in schema), error conditions, and the minItems constraint on subtasks. For a destructive tool with 4 parameters, some additional context would improve completeness.

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% (ticket and keepParent have descriptions). The description adds context about the subtasks parameter ('you provide the subtasks') and implies keepParent behavior ('deletes the parent'). However, it does not describe all parameters in detail, and the subtasks items properties lack schema descriptions.

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 ('Replace one feature with a set of linked subtasks'), specifies the resource (feature) and outcome (deletes parent, creates subtasks), and distinguishes from sibling tools like add_feature, add_features_bulk, and commit_feature by explicitly mentioning replacement and deletion.

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 for decomposing a feature into subtasks with deletion of the parent. It does not explicitly list when not to use or compare to alternatives, but the context is clear enough for an agent to infer appropriate use cases.

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