pipeline_listar

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

No annotations are provided, so the description must disclose behavioral traits. It mentions only that it lists items but omits details on pagination, filtering capabilities, result structure, or side effects. This is insufficient for an agent to predict behavior accurately.

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 a single short sentence, making it concise. However, it sacrifices necessary detail for brevity, leaving the agent underinformed. It is not poorly structured but is incomplete.

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 lack of annotations, output schema, and parameter documentation, the description is severely incomplete. It fails to cover return format, filtering possibilities, or usage constraints, leaving the agent with barely enough information to attempt use.

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 sole parameter 'filtros' has no description and 0% schema coverage. The description adds no meaning to the parameters; it does not explain valid filter keys, value formats, or constraints. The agent gains no understanding of how to construct a valid filter object.

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 uses a specific verb 'Lista' (lists) and identifies the resource as 'negociações e perfis de interesse no funil de vendas'. This distinguishes it from siblings like 'pipeline_atualizar_etapa' and 'pipeline_campos', though the term 'perfis de interesse' could be more precise.

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 guidance on when to use this tool versus alternatives. The description does not mention any prerequisites, exclusions, or context for choosing this list operation over others.

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