jira_get

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

No annotations provided, so description carries full burden. Clearly states it returns issue details including transitions, comments, attachments. Implicitly read-only, but could explicitly state it's a read 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?

Well-structured: returns, when to use, sibling tool. Slightly verbose but each sentence is informative.

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?

No output schema, but description thoroughly covers return fields, usage context, and guides to sibling tool for attachments. Handles complexity of 6 parameters with clear default-oriented descriptions.

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% with good parameter descriptions. Description adds value by indicating the tool is used after key discovery, but does not add parameter-level meaning beyond 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?

Verb+resource is explicit: 'Full details for one Jira issue'. Lists specific fields (summary, description, status, etc.) and clearly distinguishes from siblings like jira_search and jira_get_attachment.

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?

Provides concrete query patterns: 'show me FOO-123', 'what does this ticket say', and context about after discovering a key from get_dev_context or jira_search. Also explicitly says to use jira_get_attachment for viewing attachment contents.

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