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

With no annotations, the description carries the full burden and does well: it discloses ordering by depth tier, returned fields including availability basis/freshness and last_verified_at, and pagination defaults and limits. It does not describe permissions or rate limits, but for a read-only listing tool this is substantially transparent.

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-loads geography and ordering before fields and pagination. The phrase 'ordered profiled, detailed, then listed' is grammatically awkward, but the overall structure is efficient and avoids waste.

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?

Because there is no output schema, the description usefully lists many returned fields and pagination behavior. But it does not explain response structure, total counts, or offset semantics, and does not guide the agent on when to use this list versus targeted siblings like get_salon or search_merchants.

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 only 33%, so the description must compensate. It adds the useful default limit of 50 and repeats the max of 200, and restates the depth enum values already documented in the schema. However, offset is named without explaining its pagination semantics or default, leaving one parameter underspecified.

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 clearly states the resource and scope: salons in San Francisco, ordered by depth tier. It adds returned-field coverage (neighborhood, price range, stylist count, verification dates), so the agent knows what this list provides. It does not explicitly distinguish itself from siblings such as search_merchants or get_salon, keeping it below a 5.

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?

The description implies browsing the salon catalog, but gives no explicit when-to-use guidance and names no alternatives. With sibling tools like search_merchants, get_salon, and compare_options available, the agent must infer that this is the broad listing tool rather than a targeted lookup or comparison tool.

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