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

Annotations already declare readOnlyHint, openWorldHint, non-destructive and non-idempotent, so the safety profile is covered. The description adds nothing further: no mention of what the feed returns (vehicle positions vs. arrival predictions), update cadence, or coverage limits, and the 'past moment' claim is unactionable given zero parameters.

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, front-loaded sentence with no filler. It is arguably under-specified rather than verbose, but nothing in it is wasted.

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 zero-parameter live sensor feed with no output schema, the description should say what an agent will receive and how fresh it is. It says neither, and the 'past moment' clause conflicts with an empty input schema, leaving an agent unsure how to invoke it correctly.

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 no parameters, so the baseline is 4; there is nothing for the description to compensate for. The only risk is the 'past moment' phrasing implying a time argument that the empty schema does not expose.

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?

Names a specific data source and scope (MBTA buses, subway, commuter rail), so the resource is identifiable, but the verb is implicit and there is no differentiation from the sibling cell_sensor_mbta_at, which the trailing phrase 'or at a past moment' seems to gesture at.

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 guidance on when to call this versus cell_sensor_mbta_at or other transit sensors (amtrak, nyc_subway, trains_fi). Usage must be inferred entirely from the name.

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