get_line_status

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

No annotations are provided, so the description carries the full behavioral burden, and it discloses almost nothing beyond 'current' — no freshness/live-vs-cached semantics of 'current', no rate limits, and no indication of what the status result contains. 'Get' implies a read, but that is the extent of the disclosure.

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 efficient sentence that front-loads the action and resource with no filler. It is appropriately sized, though the parenthetical examples are partly redundant with the schema.

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 one-parameter read tool with no output schema, the description is minimally adequate but leaves the return shape and the meaning of 'current' unexplained. It does not round out the definition with the behavioral context that missing annotations would otherwise require.

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%, and the schema already lists example values ('elizabeth, central, jubilee, dlr...'), so the baseline is 3. The description's mode list (tube, DLR, Elizabeth line) marginally reinforces accepted inputs but adds no format or case-sensitivity detail beyond the schema.

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 ('get') and resource ('current status of a specific TfL line'), and the word 'specific' implicitly contrasts with the sibling get_all_lines_status. The parenthetical names supported modes, making the scope concrete. It does not explicitly name the alternative, but the resource is unambiguous.

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?

Usage is only implied: an agent can infer this is the single-line lookup versus get_all_lines_status for every line, but the description never states when to prefer one over the other or any prerequisites. No exclusions or alternatives are named.

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