List Available Status Transitions

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

Annotations already declare idempotent and read-only behavior. The description adds that it returns paginated JSON and requires specific parameters, but the contradictory reference to Drawings undermines trust in what the tool actually does.

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 a single paragraph that mixes accurate and inaccurate information. It is not concise, containing irrelevant details about Drawings that do not belong.

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?

No output schema exists, so the description should explain the return structure. It incorrectly states it returns Drawings instead of status transitions. Key information about the transition structure is missing.

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%, so baseline is 3. The description adds context about pagination parameters (page, per_page) and required parameters, but the erroneous mention of Drawings reduces confidence.

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 title and first sentence indicate it returns status transitions for a coordination issue, but then the description adds 'Use this to enumerate Drawings...' which contradicts the purpose and is likely a copy-paste error from another tool. This confuses the core function.

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. The description incorrectly suggests it is for enumerating Drawings, which is misleading and provides no differentiation from sibling tools.

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