workflow_epic_join

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

With no annotations, the description carries the full burden. It implies a state change (becoming an 'active participant') but says nothing about whether joining is idempotent, whether it requires authorization or an existing roster entry, what side effects occur, or how a duplicate join is handled. Only the barest behavioral hint is present.

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 filler; the verb and resource come first and the qualifying scope follows. Every clause carries information.

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 two-required-parameter mutation-style tool with no annotations, no output schema, and 0% parameter documentation, one sentence is not enough. The agent lacks permission requirements, idempotency behavior, and valid role values needed to call it correctly.

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 both parameters are undocumented in structured data. The description loosely maps 'epic' to epicId and 'role' to actorRole, but adds no format, allowed values, or examples for the role string, leaving the agent to guess what a valid role looks like.

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?

Names a specific verb (join) and resource (epic) and adds the scope 'as an active participant with a declared role', so the agent knows this is a membership action rather than a lifecycle action like workflow_epic_create or workflow_epic_activate. It stops short of explicitly contrasting itself with those siblings, so it is clear but not fully differentiated.

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?

There is no statement of when to use this versus the many workflow_epic_* siblings, no prerequisites (e.g. must the epic exist or be active?), and no exclusions. 'Active participant' hints at context but the agent is left to infer the trigger conditions entirely.

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