run_reverse_agent

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

The description adds useful behavioral context by stating termination conditions (blocked, stalled, or analysis checkpoint) and that it plans/executes iteratively. The readOnlyHint=false annotation already signals potential mutation, and the description does not contradict it, but it does not disclose side effects or state changes, which would be valuable for a tool that executes actions.

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 with no wasted words. It conveys the core behavior and termination conditions efficiently, though it could be slightly more structured to clarify the input and output expectations.

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 the tool has seven parameters, no output schema, and a complex operational concept ('reverse chain'), the description is far too brief. It does not explain what the reverse chain is, what constitutes 'blocked' or 'stalled', what the analysis checkpoint is, or what the agent's output will contain. An agent cannot make an informed decision about when and how to invoke this tool based solely on this description.

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 description provides no information about any of the seven parameters. With 0% schema description coverage, the description was expected to compensate, but it does not mention how goalMode, strategy, maxRounds, outputMode, or other parameters influence behavior. The schema's enums and defaults are self-explanatory but insufficient for selecting appropriate values without additional context.

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: it is a one-shot entry point that repeatedly plans and executes the main reverse chain until a stopping condition. This distinguishes it from some siblings by emphasizing the 'one-shot' and 'repeatedly' nature, but it does not explicitly contrast it with similar tools like 'orchestrate_reverse_task' or 'start_reverse_task'.

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: use this when you want to run the entire reverse chain automatically in one go, continuing until blocked, stalled, or reaching the checkpoint. However, there is no explicit guidance on when not to use it or how it compares to alternative tools such as 'start_reverse_task' or 'orchestrate_reverse_task'.

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