attach_tag

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It implies a write operation ('Attach') but does not disclose whether the operation is idempotent, whether it can be undone, what permissions are needed, or what happens if the tag or work item does not exist. This is a significant gap for a mutation 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?

The description is a single, concise sentence that is front-loaded with the action. It has no redundant words or filler. However, it is arguably too terse, as it omits important context that could be included without much added length, so it is not perfectly 'appropriately sized'.

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 has three required parameters, no annotations, and no output schema. The description fails to provide essential context such as return values, error conditions, idempotency, or side effects. Given the lack of annotation support, the description is incomplete for an agent to confidently invoke the tool without additional knowledge.

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%, so the description must compensate. It clarifies that tag_id refers to an 'existing tag' and work_item_id to a 'work item', but it entirely omits project_id. It does not explain the relationship between the parameters (e.g., that the tag must belong to the project) or provide any additional constraints beyond the schema.

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 a specific verb ('Attach') and clearly identifies the resource ('work item') and the object ('existing tag'). It distinguishes this tool from siblings like create_tag, detach_tag, and update_tag by implying that the tag already exists and the action is to link it. This is a precise and unambiguous statement of purpose.

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. It does not mention prerequisites (e.g., that the tag must already exist, that the work item must be in the same project), nor does it contrast with detach_tag or create_tag. The description simply states the action with no contextual usage advice.

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