Find parking facilities

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

No annotations are provided, so the description carries the full burden of behavior. It reveals that results include capacity, fee, and access information, and are sorted by distance, which is valuable behavioral context. It does not cover pagination or error cases, but these are not critical for a simple search tool.

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 a single, compact sentence that packs essential information without redundancy. It front-loads the main verb and resource and includes valuable detail about the results, scoring a 5.

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?

The tool is a straightforward search with two required parameters, a fully documented schema, and a description that specifies what information is returned and how it's ordered. Although no output schema is present, the description compensates by naming result fields, making the description sufficiently complete for AI invocation.

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?

The input schema covers all four parameters with 100% detail, including units, defaults, and types. The description adds little beyond confirming the location context and result attributes, so it earns the baseline score of 3.

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 uses the specific verb 'Locate' with the resource 'parking facilities', enumerating types (lots, garages, street parking) and key output attributes (capacity, fee, access) and sorting by distance. This clearly distinguishes it from broader sibling tools like find_nearby_places.

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 clearly implies use when the user needs parking facilities near a location, and the context of 'near a location' with distance sorting is stated. However, it does not explicitly mention when not to use it or alternatives, so it loses one point for lacking explicit exclusions.

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