Workflow

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions the tool can 'reset' workflow state, implying destructive capability, but doesn't clarify permissions needed, side effects, rate limits, or what 'reset' actually does. The Petri net reference adds some context but lacks practical behavioral details.

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 appropriately concise with two sentences: one listing actions and another providing technical context. It's front-loaded with the core purpose, though the second sentence about Petri nets could be more integrated. No wasted words, but slightly fragmented structure.

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 2 parameters, 0% schema coverage, no annotations, and no output schema, the description is incomplete. It doesn't explain return values, error conditions, or the full behavioral impact of actions like 'reset'. The Petri net context is helpful but insufficient for practical use without more operational details.

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%, so the description must compensate. It maps the 'action' parameter to four specific values (status, transition, history, reset) and implies 'transition' is used when firing transitions, adding meaningful semantics beyond the bare schema. However, it doesn't explain parameter interactions (e.g., when 'transition' is required) or provide examples.

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's purpose as managing agent workflow state with specific actions (check status, fire transitions, view history, reset) and mentions it's based on a Petri net state machine. It provides a specific verb ('manage') and resource ('agent workflow state'), though it doesn't explicitly differentiate from sibling tools like 'edit', 'system', 'vault', or 'view'.

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 lists four possible actions but provides no guidance on when to use this tool versus alternatives, when not to use it, or how it relates to sibling tools. There's no context about prerequisites, dependencies, or typical use cases beyond the action enumeration.

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