buscar_automacoes

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

No annotations provided, so description bears full burden. It states what is returned (automation with trigger and actions) but does not disclose pagination behavior, rate limits, or whether the operation is read-only. The description is straightforward but lacks depth for full transparency.

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?

Description is structured with a main line followed by numbered observations. It is relatively concise for the information provided, though could be slightly shorter. The main purpose is front-loaded.

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 description should explain return value; it does so minimally ('Retorna a automação com o gatilho e as ações configuradas'). For a search tool with 6 parameters, more detail on filtering behavior, defaults, or sorting would improve completeness. Sibling tools exist for translation, but the description references them adequately.

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 0%, so description must compensate. It explains entidade_id and etapa_id in observations, but does not add meaning for id, nome, pagina, or habilitada. With 6 parameters, only 2 are partially explained, leaving gaps for the other 4.

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?

Description clearly states the tool searches for automations (funnel or general) in Ploomes CRM and returns them with trigger and actions. It distinguishes from sibling tools like buscar_gatilhos_acoes_automacao by focusing on retrieving automations rather than translating IDs.

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 specific guidance on how to use parameters: entidade_id mapping to entity types, etapa_id for funnel stage filtering, and references to other tools for translation (buscar_schema, buscar_pipeline, buscar_gatilhos_acoes_automacao). However, it does not explicitly state when not to use this tool or compare with alternatives.

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