gbfs_get_free_bikes

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

No annotations are provided, so the description carries full behavioral burden. It discloses that data is real-time and includes battery levels and coordinates, but says nothing about authentication needs, rate limits, pagination behavior, or whether the endpoint returns empty results for systems without free-floating vehicles. For a network API call with zero annotation coverage, this is thin.

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?

A single, dense sentence that front-loads the verb and resource, then adds key value attributes (battery levels, coordinates). No filler or redundancy.

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 5-parameter network API tool with no annotations and no output schema, the description covers purpose and return content but omits behavioral context like error handling, rate limits, or data freshness caveats. It is adequate but leaves gaps for correct invocation in a production agent.

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 100%, so the schema fully documents all five parameters (limit, latitude, longitude, radius_meters, system_id_or_url). The description adds no parameter details beyond what the schema provides. Baseline 3 applies when the schema does all the work.

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 (Fetch) and resource (real-time dockless/free-floating bikes and scooters via free_bike_status.json). Clearly distinguishes from siblings like gbfs_get_stations and gbfs_get_vehicle_types by naming the exact data feed.

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?

No guidance on when to use this tool versus alternatives. It doesn't mention that free-floating vehicles are different from docked stations (gbfs_get_stations) or vehicle types (gbfs_get_vehicle_types). An agent must infer the distinction from the resource name alone.

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