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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is fully covered. The description contributes only the "current official" freshness/sourcing signal; it says nothing about refresh cadence, what happens when no filter is supplied, or what "supported operators" covers.

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 front-loaded sentence with no filler, which is efficient. It is arguably too terse for a four-parameter tool, but there is no wasted wording to cut.

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?

An output schema exists, so return values need not be described. However, for a tool with four untyped, entirely undocumented optional filters, the description leaves out how filters combine, what an unfiltered call returns, and how results are bounded — gaps the agent cannot resolve from structured fields.

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 0% across four parameters (line, mode, limit, operator), so the description carries the full burden and largely fails. "Across supported transport operators" loosely gestures at the operator filter, but line, mode, and especially limit have no meaning, format, or default guidance anywhere.

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 and resource: "Return current official disruptions and service announcements" scoped to "supported transport operators." An agent can tell this apart from istanbul_traffic_status or istanbul_water_status by the disruption/announcement framing, though no sibling is named explicitly.

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, no prerequisites, and no mention of when an agent should prefer istanbul_traffic_status, istanbul_water_status, or istanbul_next_departures instead. The word "current" is the only scoping signal, so the agent must infer the tool's role from its name alone.

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