gbfs_get_alerts

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

No annotations are provided, so the description carries the full burden. It usefully scopes the result to 'active' alerts and named disruption/weather categories, implying a read-only fetch, but says nothing about auth requirements, caching, failure modes, or result shape.

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 compact sentence that front-loads the verb and the resource. No wasted language, nothing to trim.

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 simple one-parameter read endpoint with no output schema, the description covers what the tool returns (active alerts, disruptions, weather closures) and where they come from. Only minor gaps remain around auth and response structure.

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 100% for the single required parameter (system_id_or_url), so the schema already documents the accepted ID-or-URL forms. The description adds no parameter meaning beyond what the schema supplies, which is the baseline 3 case.

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 (active system alerts, disruption notices, weather closures) plus the backing file system_alerts.json. The alert resource is clearly distinct from the sibling station/bike/vehicle-type endpoints, though no sibling is named explicitly.

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 when-to-use or when-not-to-use guidance, and no mention of alternatives among the other gbfs_* tools. Usage is only inferable from the fact that it fetches alerts.

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