feegow_get_supplier

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

No annotations are provided, and the description does not disclose behavioral traits such as read-only nature (only implied by GET method), authentication requirements, rate limits, or potential side effects. The lack of transparency is significant for a function that searches data.

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 short, including the endpoint in parentheses. It is front-loaded with the core purpose. However, the bracketed '[Financeiro]' could be omitted or integrated, but overall it is concise.

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 (1 parameter, no output schema, no annotations), the description does not fully equip an AI agent. It lacks details on the structure of the 'query' object (allowed keys, value types), the response format, and whether multiple suppliers can be returned. This is insufficient for a search tool.

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 schema describes 'query' as an object with additional properties. The description adds context by stating 'Passe os filtros conhecidos em query' (pass known filters in query), clarifying its purpose as a filter object, which is valuable beyond the schema's generic description.

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?

Description clearly states it searches for supplier information (Busca informações de um fornecedor). The verb 'busca' and resource 'fornecedor' are specific. However, it does not explicitly differentiate from the sibling tool feegow_list_suppliers, which likely lists all suppliers.

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?

There is no guidance on when to use this tool versus alternatives like feegow_list_suppliers. The description only instructs to pass filters in 'query' without explaining conditions or prerequisites.

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