getStationGroup

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

With no annotations provided, the description carries the full burden and adds valuable behavioral context: it specifies the required scope ('stations:read'), indicates it is read-only via '[READ-ONLY]', and mentions the corresponding API endpoint. This covers key aspects like authentication needs and safety, though it lacks details on rate limits or error handling.

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 highly concise and front-loaded, with every sentence earning its place: the first states the purpose, the second provides the API endpoint, and the third covers scope and read-only status. There is no wasted text, making it efficient for an agent to parse.

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?

Given the tool's low complexity (one parameter, no output schema, no annotations initially), the description is reasonably complete: it explains the purpose, authentication, and safety. However, without an output schema, it does not describe return values (e.g., what details are included), which is a minor gap for a retrieval tool.

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%, so the schema fully documents the single parameter 'stationGroupId'. The description does not add any extra meaning beyond what the schema provides (e.g., format examples or constraints), resulting in a baseline score of 3 for adequate but no additional value.

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 clearly states the verb ('Gets') and resource ('details about a specific station group'), making the purpose unambiguous. However, it does not explicitly differentiate from siblings like 'listStationGroups' (which likely lists multiple groups) or 'getStation' (which retrieves individual stations), though the specificity of 'specific station group' implies singular retrieval.

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 implies usage by specifying it retrieves details for a 'specific station group', suggesting it should be used when the ID is known, as opposed to listing all groups. However, it does not explicitly state when to use alternatives like 'listStationGroups' or provide exclusions, leaving some ambiguity for the agent.

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