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

With no annotations, the description carries the full burden and does disclose meaningful traits: results come from the business's own site, ambiguous or missing matches are returned as candidates rather than guessed, and resolution is deterministic. It also discloses cost ($0.01 via x402) and the production endpoint. Auth requirements and failure modes beyond ambiguity are not covered.

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 purpose and the never-guess guarantee are front-loaded and earn their place, but the trailing 'Deterministic. By OMENZ.' branding and the parenthetical about AYNE, the production GET URL and x402 pricing add promotional and operational noise to what should be a clean tool contract.

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 4-parameter tool with no output schema and no annotations, the description covers inputs, resolution behavior, ambiguity handling, and the shape of the returned data (phone, address, hours, notices). Only error/permission edge cases are absent, which is a minor gap at this complexity.

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 0%, so the description must compensate, and it does name a role for every parameter: url is the business website, and city/ZIP/street are location identifiers. It does not clarify whether the locators are alternatives or combinable, nor that the schema marks only url as required, leaving the 'no locator supplied' case to be inferred from the ambiguity statement.

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?

States a precise verb and resource: resolving which location page of a multi-location business the caller means, returning the matching branch page. The framing question ('which location page ... is the one you mean?') plus the return contents (phone, address, hours, notices) makes the purpose unmistakable and distinct from any sibling in the catalog.

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?

Tells the caller exactly what to supply: the business website plus a city, ZIP or street locator. It also states the fallback behavior for unresolvable input, which effectively defines the boundary condition. It does not name any alternative tool or state when not to use it, 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.