buscar_checklists_etapa

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

No annotations provided, so the description must fully disclose behavior. It describes a search operation but does not indicate whether it is read-only, pagination behavior (the 'pagina' parameter is present but unexplained), required permissions, or side effects. This is insufficient for a tool with 3 parameters and no annotations.

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 with two short paragraphs. The main purpose is front-loaded, and the 'Observacoes' section is structured. No unnecessary fluff.

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, the description should convey what the tool returns (e.g., list of checklists). It does not mention return structure, pagination details, or how it integrates with sibling tools like 'salvar_checklist_etapa'. The context is minimal for a tool with 3 parameters and significant sibling overlap.

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 must add meaning. It explains 'etapa_id' and 'id' usage in the notes, but the 'pagina' parameter is not explained at all. The added information is helpful but incomplete.

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 is for searching stage checklists in Ploomes CRM using 'buscar checklists de etapas de pipeline'. It distinguishes itself from siblings like 'buscar_etapas_negocio' by mentioning it as a prerequisite, but does not explicitly contrast with all other lookup tools.

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 explicit guidance: use 'buscar_etapas_negocio' to get etapa_id, filter by etapa_id for stage-specific checklists, or by id for a specific checklist. However, it lacks instructions on when not to use this tool or alternatives beyond the prerequisite.

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