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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds that the tool returns detail for a single station and requires an ID from nrel_alt_fuel_stations, but it does not describe output structure or any other behavior beyond what annotations imply.

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 two short sentences with no redundant wording. It front-loads what the tool does and then provides the key prerequisite for obtaining the station_id.

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 single-parameter read-only detail lookup, the description is mostly sufficient: it explains the resource, the parameter source, and the tool's role relative to nrel_alt_fuel_stations. However, 'detailed info' is somewhat vague and does not indicate what fields the result will contain, especially since there is no output schema.

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 baseline is 3. The description adds operational meaning by telling the agent to source the station_id from nrel_alt_fuel_stations results, going slightly beyond the schema's generic 'Station ID from the alt-fuel stations dataset' phrasing.

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 states a specific verb and resource: it returns 'detailed info for a single alternative fuel station by station ID.' It also names the related nrel_alt_fuel_stations tool, which clearly distinguishes this detail lookup from the broader station search/list tool.

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 gives clear workflow context: 'Get the ID from nrel_alt_fuel_stations results.' This tells an agent when and how to use the tool, but it does not explicitly state when not to use it or list alternative detail tools.

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