Get saved filter

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

While annotations already mark this as read-only, idempotent, and non-destructive, the description adds meaningful behavioral context: the filter is not executed, sharing/permits/subscriptions are never returned, and user-authored JQL is third-party data rather than instructions. This materially helps the agent reason about safety beyond the annotations.

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?

Three sentences with no filler: the first states what the tool does, the second gives the critical non-run behavior and the fix, and the third warns about shared data. Every sentence carries load-bearing information.

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 operation with one required parameter, the description covers returned fields, exclusions, source of IDs, negative behavior versus jira_search, and a data-safety warning. Nothing needed to call this tool correctly is missing.

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 100%, so the input schema already fully documents both parameters. The description reinforces that filterId is numeric and sourced from jira_list_filters, but it does not add substantial semantic meaning beyond what the schema provides; a baseline of 3 is appropriate.

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 opens with a specific verb and resource: 'Reads one saved filter by numeric id'. It enumerates exactly which fields are returned and explicitly contrasts itself with jira_search ('It does NOT run the filter'), making it easy to distinguish from sibling tools.

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?

It tells the agent when not to use this tool ('It does NOT run the filter') and names the exact alternative ('copy data.filter.jql into jira_search'). It also signals the prerequisite source of filter IDs ('from jira_list_filters'), giving clear routing guidance.

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