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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the description doesn't need to explain safety. It adds valuable behavioral details: no authentication required, returns up to 10 results, and includes addresses that other tools consume via the `business` parameter. It doesn't detail pagination or error cases, but that's minor given the read-only nature.

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 short sentences, front-loaded with the core action, followed by authentication status and return behavior. No wasted words; every sentence adds value.

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 simple search tool with one parameter and no output schema, the description covers purpose, prerequisites (no sign-in), result limit, and return format (addresses for downstream use). It's nearly complete; missing only whether results are ranked or exhaustive beyond the 10 cap.

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%, so the schema already fully documents the single `query` parameter (name or booking address, at least 3 letters). The description adds a usage example ('studio noord') but no additional semantic constraints beyond what the schema provides. Baseline 3 is appropriate.

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 businesses on ServeCounter') and names the platform, so it's clearly distinct from siblings like get_business (which presumably fetches one business by ID). It also scopes the search to businesses that take booking from assistants, adding a meaningful qualifier.

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 clear context for use: to find a business by name before using other tools, and notes 'Needs no sign-in'. However, it doesn't explicitly state when not to use it versus get_business, though the distinction is implied (search vs. retrieve by ID).

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