create_queue_autoaction

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

Annotations (readOnlyHint=false, destructiveHint=false) cover only the safety profile. The description adds useful behavioral context: the action runs periodically and updates matching issues, plus the action-object types (Transition, Update, CreateComment, Webhook, CalculateFormula). It does not explain the scheduling mechanism (intervalMillis vs calendar) that drives the recurrence, which is central behavior.

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 front-loaded sentences with no filler; the core behavior and the action-object enumeration are efficient. The parenthetical list is dense but earns its place by documenting the otherwise opaque actions payload.

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 9-parameter creation tool with a nested actions array and no output schema, the description covers the essential mechanics (what it does and the action types) but omits required-parameter expectations, the filter/query XOR, and execution-timing params. Adequate but with clear gaps for correct invocation.

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 56% across 9 params. The description usefully clarifies the nested 'actions' param by listing the action variants, which the schema leaves as opaque 'Action objects', and echoes the filter/query selection. It does not address queueId, name, active, calendar, intervalMillis, or enableNotifications. Net, it partially compensates for the coverage gap and matches the ~3 baseline for middling coverage.

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?

States a specific verb (Create) and resource (autoaction) and explains the core behavior: periodically updates issues matching filter/query. It also names the action-object variants. It stops short of distinguishing itself from the sibling create_queue_trigger, but the resource is unambiguous.

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 create an autoaction versus a queue trigger (create_queue_trigger) or macro, even though these are close siblings. No prerequisites stated, such as needing an existing queueId. The agent must infer the selection criteria.

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