nexo_workflow_replay

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

With no annotations, the description should disclose side effects (e.g., mutation of workflow state). It only states 'replay the latest checkpoints' without detailing what gets replayed, whether it is destructive, or if permissions are required.

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?

Single sentence, no unnecessary words. However, the word 'honestly' adds minimal value and could be removed for clarity.

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?

Lacks details on return values, error conditions, or behavior when limit is exceeded. Does not explain what 'replay' entails operationally.

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?

No description for the two parameters (run_id, limit). Schema coverage is 0%, and the description fails to explain their purpose beyond 'latest checkpoints'.

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 replays checkpoints to resume interrupted execution. However, it does not differentiate from sibling 'nexo_workflow_resume', which likely has overlapping functionality.

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?

Implies usage for interrupted workflows ('so interrupted execution can resume honestly') but provides no guidance on when not to use it or alternatives like nexo_workflow_resume.

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