trigger_smart_followup

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

No annotations are provided, so the description carries full burden. It indicates this is a mutation ([mutation]), requires confirmation, and has an error condition for concurrent runs. But it does not disclose what state changes occur, what side effects happen (e.g., updates to follow-up logs), or the result of a successful execution.

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 very concise: two sentences plus a tag. It is front-loaded with the core purpose, followed by a key constraint, and the mutation and requirement are noted efficiently. No superfluous information.

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 trigger tool, the description covers the essential behavior: what it does, conflict condition, and confirmation need. However, it omits information about the return value (no output schema) and what happens after a successful execution, which may be needed for subsequent tool choices.

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 input schema already provides 100% coverage with descriptions for both parameters. The description adds no extra meaning beyond the schema; it merely restates the confirmation requirement. Baseline score applies.

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 triggers Smart Follow-up analysis manually ('Ejecutar Smart Follow-up ahora'). It specifies the action and scope ('para esta tienda') and distinguishes from automatic execution, but doesn't explicitly differentiate from sibling tools like preview_smart_followup.

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 a clear when-not-to-use condition: if execution is already in progress, it returns an error. However, it does not guide when to use this tool versus alternatives (e.g., preview_smart_followup for dry-run) or mention prerequisites beyond the confirm parameter.

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