jira_filter

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

With no annotations, the description carries full burden. It discloses that 'full: true' is only for read actions and mutation responses are minimal, but lacks details on side effects of delete, rate limits, or authorization requirements.

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 well-structured with a purpose statement, action list, and a note on 'full' parameter. Every sentence provides value; no redundancy.

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?

The description adequately covers actions and parameters but does not describe return values or pagination details for list actions, which would be helpful given the absence of an output schema.

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?

Despite only 11% schema coverage, the textual breakdown of each action explicitly maps required/optional parameters (e.g., 'create: requires name, jql; optional description, favourite, sharePermissions'), adding significant meaning beyond the 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?

The description clearly states 'Manage saved JQL filters: list/get/create/update/delete plus the current user's favourites,' which precisely defines the tool's scope and distinguishes it from sibling tools like jira_issue or jira_search.

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 description provides detailed action-specific parameter requirements (e.g., 'list: optional filterName, accountId...'), but does not explicitly guide when to use this tool versus alternatives like jira_search or jira_issue for filtering operations.

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