jira_filters_update

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

Description reveals the pre-fetching and re-sending behavior for unspecified fields, which is beyond the annotations (readOnlyHint=false confirms mutation). Adds important context about the tool's internal handling.

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?

Two concise, well-structured sentences. First sentence states purpose, second adds critical behavioral detail. No unnecessary words.

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?

Tool has 4 parameters (1 required) and output schema exists. Description covers main behavior and pre-fetching. Could mention need for valid filter_id, but overall complete for an update tool.

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%, but description adds value by explaining that name and jql are required by Jira even though they are optional in the schema, and that they are auto-filled. This clarifies the actual parameter behavior.

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?

Description clearly states the verb 'Update' and the resource 'existing saved JQL filter', and lists the updatable attributes (name, JQL, description). Clearly distinguishes from sibling tools like jira_filters_create, jira_filters_delete.

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?

Explicitly explains that Jira requires name + jql on every update, and that unspecified fields are pre-fetched. This guides the agent on how to use partial updates. Does not explicitly mention alternatives but context from sibling names is sufficient.

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