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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered. The description adds real context beyond that: the response is the complete set of Q&A (implying no truncation/pagination), each item carries sources, and it decodes the 'owner-approved' status as confirmation by the verified business owner — domain semantics an agent cannot get from the schema.

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?

Two sentences, zero waste, with the core operation front-loaded and the parenthetical definition placed exactly where the ambiguous term appears.

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?

With only two well-documented params, a read-only annotation set, and no output schema, the description does the needed work by sketching the return shape. Minor gaps remain: behavior on an invalid/unknown business_id and the language fallback are unstated.

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% and both parameters are already documented there, including that business_id comes from search_business. The description restates that provenance but adds nothing about the language parameter (e.g., default behavior when omitted), so 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?

Specific verb+resource: 'Read the full profile of one business', and it goes further to name the payload — every question and answer with sources and approval status. That contrasts clearly with the sibling search_business, which finds businesses rather than returning one business's full profile.

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?

'Use the business id from search_business' gives the concrete prerequisite and chains the tool to the correct sibling. There is no explicit when-not guidance (e.g., when to prefer ask_business for a targeted question over pulling the whole profile), so it stops short of a 5.

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