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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered elsewhere. The description adds a useful behavioral note about domain targeting and the breadth of the returned payload, but says nothing about rate limits, auth needs, or what happens for an unknown ID.

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?

Purpose is front-loaded in the first sentence, followed by one sentence of payload detail and one of use cases. The field list is long but earns its place given there is no output schema; a small amount of redundancy remains between the title and the first line.

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 no output schema, the description correctly compensates by listing the return fields. Both parameters are fully documented in the schema, so the only meaningful gaps are error behavior for invalid IDs and any note on which domain to prefer when the business is ambiguous.

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 (placeId and domain) carry their own descriptions plus an enum for domain. The description only restates 'by Yelp ID or alias' and 'domain targeting,' adding no format or selection guidance beyond the schema, so the baseline of 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?

The description states a specific verb and resource — 'Fetches a single Yelp business by Yelp ID or alias' — and enumerates the returned fields, so an agent knows exactly what it produces. The distinction from siblings (search results, place reviews) is implicit in the singular, ID-based scope rather than stated outright.

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?

Three concrete use cases are given: enriching leads/listings, monitoring a competitor's rating/review count, and validating hours/amenities before display. There is no explicit when-not-to-use guidance or naming of the sibling tools as alternatives, which keeps it below a 5.

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