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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds one genuinely useful behavioral fact beyond that: distances are 'straight-line' rather than driving distance, and the index is a USGS reference set. It says nothing about result ordering, truncation, or what happens when the radius crosses state lines.

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 is correctly front-loaded in sentence one, but the remaining three sentences are defensive boilerplate ('Follow its required fields and exact choices', 'Put tool fields inside inputs') that restate schema constraints. The closing sentence about the REST calculator field is unclear enough to cost space without adding comprehension.

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?

With an output schema present, return values need no explanation, and the tool itself is simple. However, an agent still cannot tell whether results are bounded by the given state, whether limit truncates silently, or how this differs operationally from the landmarks sibling — gaps the description could have closed in one clause.

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 largely does not: it never explains what 'state' constrains (search origin vs. result bounds), what 'limit' caps, or how radiusMiles interacts with the 1-50 bound. It does clarify that all fields go inside the nested 'inputs' object, but that structure is already shown in the schema example. Worse, it references a 'units' field that does not exist anywhere in the input schema, and the 'REST calculator field' warning is opaque.

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 first sentence names a specific verb ('Find'), resource ('communities'), a quantified scope ('within 1 to 50 straight-line miles'), and a data source ('BusCalc USGS reference index'). The resource noun alone distinguishes it from siblings like buscalc_map_nearby_landmarks or buscalc_map_fuel_stops.

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 never says when to choose this tool over a sibling such as nearby_landmarks, nor any precondition for use. The only conditional guidance is mechanical ('Supply units or modelVersion only when listed in inputSchema'), which governs argument shape rather than tool selection.

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