buscar_pipeline

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

Description discloses filtering behavior (when nome_pipeline is omitted, all pipelines are returned; similarly for nome_etapa). However, it does not explicitly state that the operation is read-only (though implied by 'busca'), and the 'id' parameter present in the schema is missing from the description. No mention of authentication, rate limits, or response format.

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 concise with a clear objective and bullet-like argument list. No unnecessary text, and the emoji adds visual clarity without bloat.

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 no output schema and no annotations, the description should compensate. It explains the purpose and most parameters but omits the 'id' parameter and does not describe return structure, pagination behavior beyond page number, or output format. This is adequate but incomplete for a listing tool with 4 parameters.

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 0%, so description carries full burden. It covers 3 of 4 parameters (pagina, nome_pipeline, nome_etapa) with clear explanations of purpose and default behavior. The missing 'id' parameter is a gap, but the provided descriptions add significant meaning beyond the raw schema.

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 a list of pipelines/funnels in Ploomes CRM, with a specific verb ('busca') and resource ('lista de pipelines / funis'). It is distinguishable from sibling tools like 'salvar_pipeline' (save) and 'excluir_pipeline' (delete).

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 explicit guidance on when to use this tool versus alternatives (e.g., salvar_pipeline for creation, excluir_pipeline for deletion). The description only explains functionality but does not provide context for selection among siblings.

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