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 this is a read-only operation, nor does it mention potential side effects, permissions, or error behavior. The description lists content but lacks behavioral clarity.

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 extremely concise, providing one sentence in each language without extraneous content. It efficiently communicates the scope of the profile.

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 description enumerates the main components of the business profile (hours, rating, catalog, promotions, events, links), which is fairly comprehensive for a view operation. It does not mention pagination or response format, but that is not critical for a single-business profile retrieval.

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 already provides a description for the slug parameter ('from buscar_negocios'), and the tool description does not add additional meaning beyond that. Baseline of 3 is appropriate due to full schema coverage.

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 action ('View business profile') and the resource (business by slug). It distinguishes itself from sibling tools like buscar_negocios (search) and ver_promociones (view promotions) by focusing on a full profile given a specific slug.

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 implies usage when a slug is available and a comprehensive profile is needed. It does not explicitly state when not to use it, but the context of sibling tools provides enough guidance for an agent.

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