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

The description explicitly warns that this is not a read-only operation and discloses concrete side effects: reconciling payments, reserving balance, and resuming execution. This adds meaningful behavioral context beyond the annotations, which only indicate non-read-only and destructive hints.

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 compact and front-loaded, with three sentences that each earn their place: what it does, when to poll, and the important side-effect warning. There is no redundant or filler content.

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 single-parameter tool with an output schema, the description covers the core purpose, polling behavior, terminal states, and non-read-only side effects. It is slightly vague about when the side effects occur, but enough context is present 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 description coverage is 0%, and the description does not explain the ticket_id parameter beyond the schema's property name. The description never mentions how to obtain or format the ID, so it fails to compensate for the missing schema 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?

The description clearly states a specific action: 'Read the current state of a ticket' and adds polling intent with terminal states. It does not explicitly distinguish itself from sibling actionlayer_get_action_ticket, so it misses full sibling differentiation.

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 gives clear context for when to use the tool: poll until the state reaches one of four listed outcomes. It does not name alternatives or exclusions, but the polling guidance is a strong usage signal.

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