consultar_fornecedor

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

With no annotations, the description carries the full burden. It discloses a prerequisite (at least one identifier) and implies a read-only operation via 'consulta', but does not detail error handling, response format, or behavior when multiple identifiers are provided. It adds some value but lacks rich behavioral context.

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, concise sentence that front-loads the primary purpose and immediately follows with the key usage requirement. No filler or redundant information.

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?

The tool has no output schema or annotations, so the description must cover more ground. It addresses the tool's purpose and input requirement, but omits details about return values, potential errors when no identifier is provided, and how it differs from similar query tools. It is adequate but has clear gaps.

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%, so the description must compensate. It refers to the parameters collectively as 'identificadores' and states that at least one is needed, which adds a constraint not in the schema. However, it does not explain each parameter's individual meaning or precedence, though the parameter names are self-explanatory.

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 function: 'Consulta detalhes de um fornecedor específico' (queries details of a specific provider). The verb 'consulta' and resource 'fornecedor específico' are specific and distinguish it from siblings like 'listar_fornecedores' (list providers) and 'incluir_fornecedor' (include provider).

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 provides clear context: it's for a specific provider and requires at least one identifier ('Informe ao menos um dos identificadores'). This gives usage guidance on prerequisites but does not explicitly mention when not to use it or name alternatives.

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