jira_my_open_issues

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

With no annotations, the description carries the full burden. It discloses the core filtering behavior (unresolved, assigned to current user) but omits details such as default result limits, pagination behavior, or return format. For a simple read operation, this is adequate but not comprehensive.

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 a single, succinct sentence that front-loads the essential information. Every word earns its place, and there is no redundancy or filler.

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?

Given the tool's simplicity (one optional param, no annotations, no output schema), the description provides the basic purpose but lacks surrounding context such as how results are returned or how this relates to sibling tools like jira_search. It is minimally viable but has gaps that could lead to misuse.

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 0%, and the description does not mention the maxResults parameter at all. The agent receives no guidance on the parameter's meaning or default behavior beyond the schema's min/max constraints, failing to compensate for the lack of structured 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 the tool's purpose: 'list unresolved issues assigned to the current user.' The verb 'list' and resource 'issues' are specific, and the qualifiers 'unresolved' and 'assigned to the current user' distinguish this from sibling tools like jira_search or jira_get_issue.

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 word 'Shortcut' implies convenience over a more general search, but the description does not explicitly mention alternatives like jira_search or specify when not to use this tool. The context is clear for the intended use case, but no exclusions or alternative guidance are provided.

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