get_business_profile

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

No annotations provided, so description carries full burden. It details the data returned (localização, canais, horários, ofertas, políticas, evidências) and notes provenance with source_url. Implicitly read-only, but does not explicitly state side effects or permissions.

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?

Description is concise with bullet points and structured format. Includes an Args section but remains focused. Could be slightly tighter, but overall efficient.

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 low schema coverage (0%) and no output schema or annotations, the description is quite complete. It lists major content areas and ties to sibling tool. Does not specify output format/JSON structure, but acceptable without output schema.

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?

Only one parameter, company_id, with schema coverage 0%. Description adds crucial context: 'o id retornado por search_businesses', clarifying its origin and usage beyond the schema's minimal type.

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 'Retorna o perfil completo de uma empresa' and specifies it retrieves location, contact channels, hours, etc. It distinguishes from sibling tool search_businesses by referencing company_id from a previous search.

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?

Explicitly advises 'Use para obter o telefone/endereço verificável de um resultado antes de agir sobre ele.' And mentions 'por company_id de uma busca anterior', indicating it should be used after search_businesses. No explicit alternatives but clear context.

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