add_subtask

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

There are no annotations, so the description carries full responsibility for behavioral disclosure. It only states the action ('Add...') without mentioning side effects, prerequisites (e.g., existing work item), return value, or any side effects. This leaves the agent without knowledge of mutation effects or error conditions.

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, front-loaded sentence with no redundant information. Every word earns its place, making it highly concise and easily scannable.

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 3-parameter create operation, the description covers the core purpose but lacks contextual details such as required parameter semantics, return behavior, or any preconditions. Given the absence of annotations and output schema, a bit more context would be helpful, but the tool's simplicity partially mitigates this gap.

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 zero description coverage, and the description does not explain the parameters. Although parameter names (title, project_id, work_item_id) are self-evident to some degree, the description adds no explicit mapping or constraints beyond what the schema names provide. This fails to compensate for the schema's lack of 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 uses the specific verb 'Add' with a clear resource ('one sub-task (checklist item)') and target ('to a work item'). The parenthetical 'checklist item' disambiguates from other add_* tools like add_comment or add_dependency. It clearly states what the tool does.

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 the use case for adding a subtask to a work item but provides no explicit guidance on when to use this versus alternatives like update_subtask or create_work_item. No exclusions or alternative tool references are given, so usage context is only implicit.

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