Jira: Get Issue

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

No annotations, but description discloses it's a read-only fetch with optional payload reduction via fields/expand. No contradictions. Could mention return format but adequate for a get operation.

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?

Two sentences, front-loaded with key action and endpoint, no wasted words.

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?

Simple tool, description covers essential: fetch by key, optional field selection. Lacks mention of default return behavior but not critical for a get operation. No output schema, but not needed.

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 100%, baseline 3. Description adds value by explaining purpose of fields/expand parameters ('to reduce payload'), which goes beyond the schema descriptions.

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 'Fetch a Jira issue by key', specifying the exact endpoint and verb. It distinguishes from sibling 'jira_search_issues_jql' which searches rather than fetches by key.

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?

Usage is implied: use when you have an issue key. But no explicit guidance on when not to use (e.g., searching) or comparison to alternatives like jira_search_issues_jql.

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