generate_retry_message

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

No annotations are provided, so the description carries full burden. It describes inputs and output but does not disclose behavioral traits like idempotency, side effects, or read-only nature. The tool appears to be a pure function, but this is not explicitly stated. Minimal transparency beyond functional description.

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 that are concise and front-loaded. Every sentence provides essential information without redundancy. The structure is clear and efficient.

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 string generation tool with 3 parameters and no output schema, the description covers inputs and the output's purpose. However, it does not describe the output format or provide examples, which would be helpful for an agent. Given the tool's simplicity and lack of annotations, the description could be more complete.

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 coverage is 0% (no parameter descriptions in schema). The description names the three parameters (tool_name, validation_error, attempted_args) and indicates their roles, but does not elaborate on expected formats, constraints, or examples. It adds value over the raw schema but does not fully compensate for the lack of schema descriptions.

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 specifies the tool's purpose: building a canonical LLM-facing retry feedback message given tool_name, validation_error, and attempted_args. It includes the formatting method (agentvet's ToolArgError.toLLMFeedback()), and distinguishes from siblings (lint_tool_definition, validate_tool_args) by its unique output.

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 implies when to use this tool—when generating a retry message after a validation error. It notes that the wording matches runtime callers, but does not explicitly state when not to use it or compare to alternatives. However, the siblings are sufficiently different, so no confusion.

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