lookupJiraAccountId

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

The annotations already declare readOnlyHint, idempotentHint and openWorldHint, so the safety profile is covered and the description does not contradict it. However, the description adds no behavioral context beyond the annotations — nothing about ambiguous name matches, permission requirements, or what the lookup returns.

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 efficient sentence with the resource and lookup keys front-loaded and no wasted words. It is appropriately sized for a simple lookup tool, though it could carry one more clause of routing guidance without bloating.

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 lookup with no output schema, the description covers the core operation adequately. It is incomplete regarding the undocumented maxResults parameter and the fact that name lookups can return multiple/ambiguous results.

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 only 50%: query is described but maxResults is undocumented in both schema and description. The description's 'display name or email' merely restates the query field, so it does not compensate for the missing maxResults semantics (defaults, limits, pagination).

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 states a specific verb (look up) and resource (Jira user account ID) plus the accepted input forms (display name or email). It is clear on its own, but it does not differentiate itself from the adjacent getJiraUser / getJiraCurrentUser siblings that plausibly retrieve user data.

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 when-to-use guidance and no mention of alternatives, despite several nearby tools (getJiraUser, getJiraCurrentUser) that an agent could confuse this with. The agent is left to infer that this tool specifically resolves a name/email into an accountId.

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