list_jira_automations

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

With no annotations provided, the description carries full burden. It states that the tool 'Returns a summary of each rule: name, trigger type, number of conditions/actions, enabled state' and provides a post-call instruction. This is adequate for a read-only list operation, though it does not disclose auth needs or rate limits.

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 consists of three concise sentences that are front-loaded: the first states the purpose, the second gives usage context, and the third describes the return format and next step. No unnecessary words or repetition.

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?

Although there is no output schema, the description explains exactly what is returned. The tool is simple with one optional parameter documented in the schema. For a list tool used in a migration workflow, the description is complete and provides all necessary information.

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 input schema has 100% coverage for the single parameter 'project_key', and the schema description already explains its meaning. The main description does not add additional parameter semantics beyond what the schema provides, so the baseline score 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 states 'Lists all Jira Automation rules visible to the authenticated user.' This is a specific verb+resource combination that clearly indicates the tool's function, and it is distinguishable from sibling tools like analyze_jira_automation and build_jira_automation.

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 explicitly says 'Call this when the user wants to migrate Jira automations to ServiceNow Flow Designer,' providing clear context for when to use the tool. Although it does not mention when not to use it or name alternatives, the context is sufficient given the sibling tools.

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