Get User Profile

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

The readOnlyHint annotation already declares this as a read operation, and the description aligns with that ('Retrieve'). The description adds no extra behavioral context such as permissions, response size, or rate limits, but it does not contradict the annotation. Since annotations cover the safety profile, this is adequate.

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 exactly one sentence, front-loaded with the main action and resource, with zero redundant words. It is perfectly concise and well-structured.

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 simple one-parameter read tool, the description combined with the rich input schema, output schema, and readOnlyHint annotation provides complete context. No additional prerequisites or limitations are necessary to understand the tool's function.

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%; the parameter user_identifier has a detailed description with examples (email, username, account ID, Server/DC key). The tool description adds no extra meaning beyond reinforcing that it's for a specific user, so the high schema coverage earns the baseline.

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 'Retrieve profile information for a specific Jira user' uses a specific verb ('retrieve') and a clear resource ('profile information' for a user). It distinguishes itself from sibling tools like jira_search_assignable_users by emphasizing a specific user with an identifier, not searching or assigning.

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 'for a specific Jira user' implies the tool is used when you already know the target user. However, the description does not explicitly state when to choose this over alternatives (e.g., jira_search_assignable_users to find a user, or confluence_search_user for Confluence users) nor provide any exclusion guidance.

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