retry

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

Discloses key behavioral traits: retries on failure, prior error as context, type validation retry logic. Lacks details on final failure behavior, side effects, or idempotency. With no annotations, description is decent but not fully comprehensive.

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?

Purpose stated upfront, followed by a bullet-like Args list. No redundant sentences, but could be slightly more concise by integrating defaults inline.

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?

Covers main functionality but omits behavior after all retries exhausted, error handling, and does not reference output schema. For a 7-param tool with output schema, more completeness is expected.

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%, but description provides brief explanations for each parameter, e.g., 'The task prompt' for prompt. Adds some meaning but lacks detail on constraints or formats.

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?

Clearly states the tool runs a single agent with automatic retries on failure, and explains the type validation retry condition. Distinguishes from siblings like 'run' (no retries) and 'chain' (multiple agents).

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?

Provides clear context for usage: when retries are needed or type validation is desired. However, does not explicitly state when not to use or compare to alternatives like 'run' or 'beam'.

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