jira_get_user

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

Annotations already declare readOnlyHint=true, so the safety profile is covered, but the description adds nothing beyond that: no indication of what happens when the username does not exist, whether it returns a partial or full user object, or which Jira deployment it targets. A single phrase that merely restates the operation leaves the behavioral picture thin.

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 short sentence with the operation front-loaded and no filler. It is efficient, though the brevity comes at the cost of the disambiguating detail it omits.

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?

With an output schema present, return values need not be described, and readOnlyHint covers safety. But for a lookup tool competing with multiple user-search siblings, the description is not complete enough to route the agent 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 description coverage is 100% and the schema itself explains the important Server-vs-Cloud distinction of `name` vs `accountId`. The description only repeats "by username" and adds no syntax, format, or edge-case detail, so this is the baseline 3.

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?

States a specific verb and resource ("Get a user"), so the action is unambiguous. However, it does not distinguish this tool from the very similar siblings find_jira_user, jira_search_users, and jira_get_current_user, leaving the agent to guess which user-lookup tool is appropriate.

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 guidance on when to use this tool versus the three sibling user-lookup tools. The description neither states prerequisites nor names an alternative, so selection between jira_get_user, find_jira_user, and jira_search_users must be inferred from the name alone.

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