buscar_numero_funcionarios

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

No annotations are provided, so the description carries the full burden. It does not explicitly state that the tool is read-only, has no side effects, or specify any behavioral traits. The description implies a lookup operation but lacks explicit disclosure of safety or consequences.

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: two sentences with one bullet point. It front-loads the main purpose and provides a key usage note. Every sentence is relevant and there is no unnecessary text.

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?

For a simple lookup tool with no output schema, the description covers the essential purpose and a primary use case. However, it does not describe what the tool returns (a list of options) or any limitations. It is minimally adequate but could be more complete.

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% (no parameter descriptions in the schema). The description does not explain the meaning or usage of the parameters (id, nome, pagina). Although parameter names are somewhat intuitive, the description should compensate for the lack of schema documentation, but it does not.

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 opcoes de numero de funcionarios no Ploomes CRM' (search for number of employees options). It specifies the resource ('opcoes de numero de funcionarios') and the action ('buscar'). The note about using it to obtain NumberOfEmployeesId distinguishes it from 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?

The description includes a usage note: 'Use para obter o NumberOfEmployeesId ao criar/atualizar um cliente.' This provides clear context on when to use the tool (during client creation/update). It does not explicitly mention when not to use it or alternatives, but the single-use case is well-defined.

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