Look up a business

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

Annotations cover the safety profile (readOnlyHint=true, openWorldHint=true), and the description adds substantial value beyond that by enumerating the returned payload: services with service_id, duration, price in BRL, opening hours, address, contact, and booking availability. Without an output schema, this return-shape disclosure is exactly what an agent needs; only minor gaps remain (no mention of not-found/error behavior).

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?

Three sentences, front-loaded with the action and identifier, then the return contents, then the dependency hint. No filler; every clause carries information an agent can act on.

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?

For a one-parameter read-only lookup with no output schema, the description supplies the identifier forms, the fields returned, and the ordering prerequisite. It is nearly complete; only failure modes (invalid slug, unknown business) are left unspecified, which is a minor gap for a low-risk read.

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 100%, and the parameter's own description already gives both accepted forms with examples. The description's 'booking link or slug' restates that, adding no syntax or validation detail beyond the schema, so the baseline 3 applies.

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?

States a specific verb and resource ('look up a business on Vitta') plus the two accepted identifier forms ('booking link or slug'). This is clearly a lookup operation, distinguishable from the appointment-oriented siblings (find_available_slots, book_appointment, cancel_appointment) without opening any schema.

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 instructs 'Call this first: the other tools need a service_id from here,' establishing ordering and dependency relative to the sibling tools. An agent knows exactly when to reach for this tool versus the booking/cancel tools.

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