salvar_filtro_checklist

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

With no annotations, the description carries the full burden. It explains the conditional logic for filter creation based on the checklist name (three cases). However, it does not disclose side effects, authentication requirements, or what the tool returns. The behavioral context is moderate but not exhaustive.

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 concise: two sentences and a bullet list. Every sentence adds value, and the structure is front-loaded with the main purpose before the observations. No waste.

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?

Given the tool's simplicity (one parameter, no output schema, no annotations), the description adequately covers the filter creation logic. However, it could briefly mention the purpose of the filter (e.g., used in checklists) or any prerequisites. Still, it is sufficiently complete for an agent to understand and invoke the tool correctly.

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 provides minimal info (name and type for 'nome_checklist'). The description adds significant meaning by explaining how the parameter value determines the filter logic (three cases). This compensates for the 0% schema description coverage.

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 that the tool creates the default filter used by step checklists in Ploomes CRM. It provides specific behavior for different cases (Pessoa Física, Empresa, others), which distinguishes it from similar tools like 'salvar_checklist_etapa' that likely save the entire checklist.

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 implies usage context (creating filters for checklists) but does not explicitly state when to use this tool versus alternatives. No exclusions or alternative tool names are provided. For example, it doesn't mention when 'salvar_checklist_etapa_completo' might be more appropriate.

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