get_issue

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

No annotations provided, so description carries full burden. 'Get' implies a read-only operation without side effects, but it does not explicitly state that it requires read permissions, is safe, or that no modifications occur. Lacks disclosure of rate limits or auth needs beyond typical Jira API expectations.

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 with a clear structure: purpose statement followed by parameter documentation. No fluff, example provided, and critical information is front-loaded. Every sentence earns its place.

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 read tool with two parameters and an output schema, the description is complete. It covers input details and scope. Output behavior is handled by the existing output schema, so no need to describe return values.

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?

With 0% schema description coverage, description compensates fully. It explains issue_key format with a concrete example and clarifies the fields parameter as an optional comma-separated list defaulting to all fields, adding significant meaning beyond bare schema.

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?

Clearly states 'Get a single Jira issue by key', specifying verb, resource, and method. Example with key format (PROJ-123) reinforces exact usage. Distinguishes from siblings like search_issues (multiple issues) and create_issue (creation).

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?

Implies usage when you have a specific issue key, but does not explicitly contrast with alternatives like search_issues for batch retrieval or get_project for project details. No when-not-to-use guidance, though the narrow scope is inferred.

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