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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is fully covered. The description adds useful context that this is a bounded local dataset of 724 listings and that distance sorting activates only with near_lat/near_lng, but says nothing about result format or pagination/limit behavior.

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?

Four short sentences, front-loaded with the dataset and the 'all filters optional' default, then per-parameter hints. Dense and waste-free, though the terse 'x = y' format occasionally reads like schema notes rather than guidance.

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 15-parameter tool with no output schema and no annotation help on filtering semantics, the description covers under half the parameters and never explains how the boolean filters or price cap behave. An agent would have to guess at the meaning and interaction of most of the surface area.

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% across 15 parameters, so the description carries the full burden — yet it only explains place, category, near_lat/near_lng and radius_km. It leaves query, amenity, limit, max_monthly_price and six boolean filters (open_now, open_sunday, open_24_hours, bookable_only, has_free_trial, contactable_only) entirely undocumented.

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 and resource ('Search Point Pleasant Local (724 listings)') and scopes the dataset size, so an agent knows this is the broad directory search rather than a single-record lookup like get_business. It doesn't explicitly name which sibling to use for pure place or category enumeration, but the intent is unambiguous.

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?

'All filters optional' tells the agent it can call with zero args, and 'category = a name from list_categories' routes one step to a sibling. There's no guidance on when to prefer search_businesses over list_places or get_business, and no note on how filters combine or whether they AND together.

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