buscar_etapas_negocio

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

No annotations are provided, so the description must convey behavioral traits. It only states that the tool performs a search, implying read-only behavior, but it does not explicitly mention that it is safe, what side effects it might have, or any authentication or rate-limiting considerations. The description lacks depth in disclosing behavior beyond the basic operation.

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 extremely concise: two main sentences plus two observation points. It is front-loaded with the primary purpose and immediately useful usage context, with no redundant or filler content.

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 simplicity of the tool (3 optional parameters, no output schema, no annotations), the description is incomplete. It lacks details about return format, pagination behavior (despite a 'pagina' parameter), and what happens when no filters are applied. The observations only partially address the pipeline filter.

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?

With 0% schema description coverage, the description adds some meaning for the 'pipeline_id' parameter ('Filtre por pipeline_id para ver as etapas de um funil especifico'), but it does not explain the 'nome' or 'pagina' parameters. This partial coverage provides some value but leaves gaps.

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's purpose: 'Buscar etapas de negocios no Ploomes CRM' (search business stages). It also specifies a concrete use case: to obtain StageId when creating/updating a business, which effectively distinguishes it from sibling tools like 'buscar_etapas_venda' and 'buscar_status_negocio'.

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 explicitly says 'Use para obter o StageId ao criar/atualizar um negocio' (Use to obtain StageId when creating/updating a business), providing clear guidance for when to apply the tool. It also mentions filtering by pipeline_id. However, it does not explicitly state when not to use 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.