Perfil completo de un negocio

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

No annotations are provided, so the description carries full burden. It clearly states what the tool returns: profile, reviews, and social networks. It implies a read operation without side effects. Though it does not detail rate limits or authorization, the behavior is straightforward and well-described.

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 consists of two concise sentences. The first sentence states the core functionality, and the second adds a usage hint. Every word is valuable, with no redundancy or unnecessary detail.

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?

Without an output schema, the description provides essential context about the return content (ficha, reviews, social networks). While it lacks detailed structure, the level of detail is sufficient for an agent to understand the tool's output. The sibling tools complement, but this description is self-contained enough.

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 coverage is 100% with all three parameters (language, place_id, max_reviews) having descriptions. The tool description does not add extra meaning beyond the schema, except noting that social networks are detected from the website. Since parameter descriptions are already clear, a baseline score of 3 is appropriate.

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 returns the full business profile including listing, reviews, and social networks detected from the website. The verb 'Devuelve' (returns) and the specific components distinguish it from sibling tools like get_business (likely returns only listing) and get_reviews (only reviews). The phrase 'insumo ideal antes de generar el prompt de la página web' provides purpose context.

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 explicitly mentions this tool is ideal before generating a webpage prompt, indicating a primary use case. However, it does not provide guidance on when not to use it or mention alternative tools. The sibling list includes get_business and get_reviews, but no comparative usage notes.

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