jira_filter

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

With no annotations, the description must disclose behavioral traits. It notes that mutation actions reject 'full: true' and read actions can return raw response. However, it omits potential side effects (e.g., deletion is irreversible) and auth requirements. Additional context would improve agent decision-making.

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 top-level description is concise (one sentence). The schema description is well-structured: a summary, bullet-point actions, and a note on 'full'. It is front-loaded but slightly verbose; could be more terse while retaining clarity.

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 complexity (18 params, multiple actions), the description provides action-specific parameter guidance and behavioral notes. However, it lacks details on return values, pagination for list, and error handling. An output schema is absent, so the description should cover these gaps.

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 only 11%, but the description compensates by grouping parameters per action (e.g., list: filterName, accountId...). It adds meaning beyond the bare schema but lacks detailed semantics for most parameters (e.g., sharePermissions is left as empty 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?

The description clearly states 'Manage saved JQL filters: list/get/create/update/delete plus the current user's favourites.' This provides a specific verb and resource, and distinguishes it from sibling tools like jira_search (issue search) and jira_issue (issue management).

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 schema description includes action-specific parameter lists and required/optional notes for each action (e.g., list, get, create). However, it does not explicitly state when not to use this tool versus alternatives, nor does it provide exclusion criteria.

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