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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=false and destructiveHint=false, so the safety profile is covered. The description adds nothing on the traits that actually matter for a live transit feed — data freshness, refresh cadence, geographic scope, or error/empty behavior when a line is out of service.

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 short noun-phrase, front-loaded with the resource and free of filler. It is terse to the point of being a fragment rather than a sentence, but every word carries information.

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?

With no output schema and no parameters, the description is the only place an agent can learn what comes back, and it names only three attributes (trains, next stop, heading) without saying whether these are per-train records, live vs. scheduled, or scoped to the whole system. Minimally usable, but thin for a sensor tool whose output shape is otherwise undocumented.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; the baseline of 4 applies. The description neither contradicts nor needs to supplement the empty 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?

The description names the resource (New York subway trains) and the data facets (next stop, destination), which goes beyond the bare name. However, there is no verb — it does not say whether it lists, queries, or streams trains — and it does nothing to distinguish itself from the sibling cell_sensor_nyc_subway_at, which appears to be a variant of the same 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?

There is no when-to-use guidance at all: no indication of when to prefer this over cell_sensor_nyc_subway_at, whether results are a live snapshot, or whether the caller should filter by train or line after retrieval. For a zero-argument feed tool that always returns everything, an explicit statement of scope would have been cheap to add.

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