Get Workflow Information

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

The description accurately describes the read behavior (no side effects). Without annotations, it carries the burden but does not disclose potential errors (e.g., item without workflow) or authentication needs. No contradiction with annotations (none provided).

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?

Two sentences: one functional statement and one example. Every word earns its place; no redundancy.

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 simple tool with one parameter and no output schema, the description is sufficiently complete. It states what is returned (state and transitions). It could mention the structure of transitions, but that is minor.

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?

The input schema has 100% coverage with a description for 'path'. The description adds value with an example showing usage format, though it doesn't elaborate further on semantics.

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 explicitly states the tool shows current workflow state and available transitions for a content item, with a concrete example. It clearly distinguishes from sibling tools like plone_transition_workflow that perform actions.

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 is implied (e.g., before transitioning), but no explicit when-to-use or when-not-to-use guidance is provided. No comparison to alternatives is given.

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