jira_groups_add_user

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

The description confirms a write operation (matching annotations) and specifies the return format. It does not disclose potential error conditions (e.g., duplicate membership, non-existent group) or side effects. The return object is described, adding some value beyond annotations.

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 three sentences, each serving a clear purpose: action, prerequisite, return format. No redundant 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?

Given the tool's simplicity and the presence of both input schema and annotations, the description covers the essential action and return format. However, it lacks error handling notes or permission requirements, leaving some gaps.

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?

Input schema coverage is 100% with clear parameter descriptions. The description reinforces using account_id from jira_users_search, but adds little new semantic meaning 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 clearly states the action ('Add a user to a Jira group') and resource. While it distinguishes from sibling group tools implicitly by its name and action, it does not explicitly compare with other group operations like creating or removing groups.

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?

Provides a useful prerequisite: 'Always verify user identity first with jira_users_search.' However, it offers no guidance on when not to use this tool (e.g., if the group does not exist) or alternatives like jira_groups_create or jira_groups_remove_user.

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