jira_execute

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

The description explicitly states these are side-effects on existing issues, indicating mutational behavior. Without annotations, it carries the burden and does so adequately. However, it does not detail authorization needs or specific impacts beyond 'state changes', which would be beneficial.

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 three sentences plus an example, all front-loaded with the core purpose. Every sentence adds value: purpose, sibling differentiation, help suggestion, and illustrative example. No wasted 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?

For a tool with only 2 parameters and no output schema, the description covers the main usage pattern and provides a discovery mechanism (help). It could mention return values or list common operations, but it's mostly complete for initial use.

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 0%, so the description must compensate. It explains that params is a flexible object depending on the operation and provides a concrete example with 'issue_key' and 'transition_id'. This adds significant meaning beyond the bare schema.

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 clearly states the tool triggers Jira state changes (transition, assign, unassign), with a specific verb and resource. It distinguishes itself from siblings by explicitly contrasting with jira_write as side-effects on existing issues rather than resource creation.

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 provides explicit when-to-use advice: 'Distinct from write because these are side-effects on existing issues rather than resource creation.' It also suggests calling with operation='help' to list all available operations, guiding the agent on how to discover usage.

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