jira_list_automation_rules

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

No annotations provided, so the description carries the full burden. It mentions routing details (JWT, tenant, company scope) which are infrastructure, not behavioral traits like read-only, permissions, or whether results are paginated. Minimal behavioral disclosure.

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 short (3 sentences) but includes redundant phrasing ('Jira connector operation') and an infrastructure detail that may not be helpful. It is acceptable in length but could be more focused and front-loaded with essential 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?

Given the existence of an output schema, return values need not be explained. However, the description does not clarify the input argument structure or the tool's core function beyond the name. For a list tool with a complex JSON input, this is incomplete.

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?

The sole parameter 'arguments' is described as 'JSON string of arguments for the connector operation.' This is generic and adds no meaning beyond the input schema. Schema coverage is 0%, yet the description fails to explain what keys or values the JSON should contain.

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 states it is the 'list_automation_rules' operation for Jira, clearly indicating the action (list) and resource (automation rules). However, it does not specify scope or differentiate from sibling Jira tools like jira_list_projects, but the name is sufficiently distinct.

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?

No guidance on when to use this tool versus alternatives. It does not mention prerequisites, when not to use, or provide context among the many sibling Jira tools.

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