recomendar_flujoDevuelve el flujo recomendado de tools según la situación: agente nuevo (diseño desde cero) o agente existente (mejora). Llamala PRIMERO si no sabés por dónde empezar.
| Name | Required | Description | Default |
|---|---|---|---|
| situacion | Yes | 'nuevo' = diseñar un agente desde cero; 'existente' = mejorar un agente que ya está definido o en producción. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It states the tool returns 'el flujo recomendado de tools', but does not specify the output format (e.g., ordered list, text, or structured data). For a simple recommendation tool, this is acceptable but could be more transparent.
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 concise sentences that front-load the purpose and usage guidance. No unnecessary words. Every sentence earns its place.
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?
The description covers the core purpose, usage context, and parameter semantics. However, it omits the return value structure, which would help an agent process the output. Given the tool's simplicity and lack of output schema, this is a minor gap.
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 single parameter 'situacion' has a clear enum with values 'nuevo' and 'existente', fully described in the schema. The tool description adds valuable context by explaining when to choose each value, going beyond the schema's built-in description.
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 title and description clearly state the tool recommends an order of tools based on the situation (new vs. existing agent). It also explicitly says to call it first when unsure where to start, differentiating it from sibling tools that focus on specific tasks like auditing or designing.
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 provides strong when-to-use guidance by stating 'Llamala PRIMERO si no sabés por dónde empezar.' It also distinguishes the two situations: 'nuevo' vs. 'existente'. However, it does not explicitly state when not to use the tool or name specific alternatives beyond the sibling list.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Tools are mostly distinct with clear purposes, but some overlap exists between auditing and reviewing tools (e.g., auditar_contexto vs. revisar_rol_y_frontera). The meta-tool recomendar_flujo might cause initial confusion but descriptions clarify its role.
All tool names follow a consistent verb_noun pattern in Spanish (e.g., aplicar_challenger, auditar_contexto). The naming is uniform and predictable across all 18 tools.
18 tools is well-scoped for the server's purpose of comprehensive agent governance. Each tool covers a distinct aspect of the agent lifecycle without being overwhelming.
The tool surface covers the full lifecycle from evaluation, design, auditing, contract generation, to final construction. No obvious gaps; the set is self-contained for agent governance.