create_list_from_inactive

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 mutation via the '[mutation]' tag but does not disclose side effects (e.g., whether contacts are removed or if the list is static/dynamic), required permissions, or data limits.

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 a single sentence plus a mutation tag, which is concise and to the point. No unnecessary words, though a slightly more structured format could improve readability.

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?

No output schema exists, so the description should explain the outcome more thoroughly. It fails to specify what the resulting list contains (e.g., all inactive contacts or a snapshot), whether it's static or dynamic, and if any data is altered.

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 100%, so the description adds minimal meaning beyond the schema. The description's reference to 'periodo determinado' loosely maps to the 'days' parameter, but no additional context or constraints are given.

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 creates a new list from inactive clients based on a period of no conversation. The verb 'creates' and resource 'clientes inactivos' are specific. However, it does not explicitly differentiate from sibling tools like create_list_from_followup, which also creates specialized lists.

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?

No guidance is provided on when to use this tool versus alternatives such as create_contact_list or create_list_from_followup. The description implies usage for inactive clients but lacks explicit conditions, exclusions, or context for selection.

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