workflow_epic_attach_ticket

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

With no annotations, the description carries the full behavioral burden. It hints that only active epics accept tickets, but says nothing about idempotency, what happens if the ticket is already attached, permission requirements, or failure modes for an operation that mutates epic state.

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, front-loaded sentence with no wasted words. It is efficient, though the brevity is partly why contextual gaps remain.

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 3-parameter, all-required mutation tool with no annotations, no output schema, and 0% parameter documentation, the description is too thin. It covers the basic action but leaves the agent without enough context to invoke it confidently.

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 coverage is 0%, so the description must compensate. It only clarifies the 'channel' parameter by listing enum values already present in the schema, and does not explain what epicId or ticketId must refer to, nor the relationship between the ticket and the epic.

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 states a specific verb ('Attach') and resource ('a channel ticket ... to an active epic'), making the operation identifiable. It does not explicitly differentiate itself from siblings like workflow_epic_add_dependency or workflow_epic_create_change_request, so it falls short of a 5.

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 phrase 'to an active epic' implies a precondition (the epic must be active), which is useful. However, there is no guidance on when to use this tool versus alternatives such as workflow_ticket_advance or workflow_epic_join, and no exclusions or prerequisites are spelled out.

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