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

Annotations already establish read-only, idempotent, non-destructive, closed-world behavior. The description adds meaningful context beyond that: the sort order (rating then review count), the review-count floor with its default, and the ratings source with an as-of date caveat.

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?

Front-loaded with use cases, then ranking mechanics, in two tight sentences with no filler. Every clause carries information.

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?

An output schema exists, so return values need no explanation, and the ranking/source semantics are covered. The one gap is the unexplained `limit` parameter, whose behavior an agent must guess.

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 only 33%, with only `topic` described. The description compensates by illustrating topic values and stating the min_reviews default of 50 (not in schema), but `limit` is never mentioned and its role is left unexplained.

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 specific verb (ranks) and resource (places in the Gilbert First directory) plus the exact ranking criteria (Google rating, then review count). This is clearly distinct from siblings like gilbert_business_lookup or gilbert_events without needing to open any schema.

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?

Concrete example queries ("best brunch in Gilbert", "top coffee shops") make the intended invocation context obvious. It does not explicitly name which sibling to use for non-ranking lookups, so routing against alternatives is left slightly implicit.

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