monitorear_cambios_recientes

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

No annotations are provided, so the description carries full burden. It discloses internal conversion of minutes to milliseconds and hints at pagination via parameters. However, it does not mention rate limits or output format, but overall it adds useful behavioral context.

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 three sentences with no wasted words. It is front-loaded with the core functionality, followed by ideal use and an internal detail. Highly concise and well-structured.

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 tool has 5 optional parameters and no output schema. The description explains the purpose and filter combinations but does not describe the output structure (fields returned, pagination behavior). It is adequate but leaves gaps for an agent to fully understand the response.

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 100%, giving a baseline of 3. The description adds value by explaining the conversion of 'minutos' to milliseconds and providing usage examples (e.g., '60 = última hora'), beyond the schema's documentation.

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 verb 'Busca' (searches) and the resource 'Compras Ágiles' with a specific time filter (creadas o modificadas en los últimos N minutos). It distinguishes itself from siblings like 'buscar_compras_agiles' which likely lacks the time filter.

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 says 'Ideal para monitoreo de nuevas oportunidades de negocio y alertas en tiempo real', providing clear use cases. It also mentions combinability with state and region filters, but does not explicitly state when not to use or contrast with alternatives.

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