jira_user

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

No annotations provided, so the description carries the full burden. It describes each action's behavior, notes that 'full:true' is rejected on mutation actions, and mentions summary projection. It does not explicitly state that all actions are read-only, but that is implicit from the context.

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 verbose and repeats information from the schema's description field. It is front-loaded with the main purpose, but the length could be reduced without losing clarity.

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 14 parameters, low schema coverage, and no output schema, the description covers all five actions, their parameter groups, and the 'full' flag. It does not describe return format, but that is reasonable for a lookup tool.

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 low (21%), but the description compensates by grouping parameters per action (e.g., search: query, accountId, startAt, maxResults, property). It adds meaning beyond the schema, though some parameters (property, sessionId, username) lack individual explanation.

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 it is for looking up Jira users and enumerates five distinct actions (myself, search, get, assignable, bulkGet), immediately distinguishing it from sibling tools like jira_issue or jira_search.

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 provides explicit guidance on when to use each action, including required/optional parameters. It also explains the 'full' flag behavior. However, it does not explicitly differentiate from other tools that might also return users (e.g., jira_search), leaving some ambiguity.

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