reiniciar_solicitud

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

With no annotations, the description fully discloses the behavioral consequences: all captured data is lost ('Se pierden todos los datos capturados hasta el momento') and the widget returns to the first step with empty fields. This gives the agent a complete picture of the side effects.

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 two concise sentences, front-loaded with the core action and consequence, followed by usage examples. No redundant information is present.

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 reset tool with no parameters and no output schema, the description covers purpose, behavior, and usage triggers. It is complete for the agent to understand when and how to invoke it.

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 tool has zero parameters, and the schema confirms this with an empty properties object. The description adds no parameter-specific details, but none are needed; the baseline for 0-parameter tools is 4.

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 function: 'Descarta la solicitud actual y devuelve al usuario al primer paso del flujo' which specifically identifies the resource (the request/application flow) and the action (discard and reset). It distinguishes from siblings like 'iniciar_solicitud_prestamo' by focusing on resetting an existing request rather than starting one.

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?

It explicitly tells when to call: 'Llámala cuando el usuario te pida empezar de nuevo' with concrete example phrases, giving the agent clear trigger conditions for when this tool is the right choice.

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