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

The annotations already declare readOnlyHint and openWorldHint, so the description is not responsible for the full safety profile. It adds useful behavior: matching is name-only, and results include a stable id usable with get_profile and ask_business. It does not describe pagination or result-limit behavior, but the core behavior is clear.

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 compact and front-loaded: the purpose comes first, followed by return-ID guidance, an example, and the key exclusion. Every sentence earns its place.

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?

There is no output schema, so the description appropriately explains that matching businesses and a stable id are returned. It also explains how to use that id downstream. The main remaining gap is result-limit behavior, which is not described.

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 moderate at 67%. The description reinforces that query is a business name with optional city/country and gives a concrete example, but it does not explain the limit parameter or the language parameter's effect. The schema already describes query and language, so the description adds only marginal parameter value.

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: find a business by name, optionally with city/country. It distinguishes itself from the category-browsing sibling discover_businesses and mentions that returned IDs work with get_profile and ask_business.

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?

It gives explicit when-to-use guidance: use this for business-name lookup, including an example query, and explicitly excludes category browsing by directing that case to discover_businesses. This is exactly the routing information an agent needs.

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