Get available transitions

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

The description provides behavioral insights by explaining that the output includes organic weighted-graph options, forceTransition-acceptable states, and valid Pomodoro events, and notes that CatStateMachine has no transition validation. However, it does not disclose side effects, auth requirements, or whether the tool is read-only.

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 sentence but is somewhat long and uses punctuation that may reduce clarity. It contains useful information but could be restructured for better readability.

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 no parameters or output schema, the description covers the main return types but lacks details on edge cases, prerequisites, or references to external documentation for deeper context.

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?

With no parameters, the description adds value by explaining what the output contains (three categories of transitions). However, it does not describe the return format or structure, which would help the agent interpret results.

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 returns transitions reachable from the current state, listing three specific categories. This distinguishes it from sibling tools like get_current_state (which returns state) and trigger_event (which triggers an action).

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?

Usage context is implied: the tool is for exploring transitions before triggering events or force transitions. However, no explicit guidance on when to use versus alternatives, and no mention of prerequisites or when not to use.

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