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

With no annotations, the description carries the whole burden, and it does disclose the meaningful behavior: the implicit condition = Poor filter and the two-key sort order, which an agent could not infer from the name. It says nothing about result size, whether limit is capped, or what each result contains, leaving the read/return profile thin.

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?

Three short clauses, front-loaded with the resource and filter, then ordering, then the trigger phrase. No filler, no restatement of the title.

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 two-parameter read-only query with no output schema, the description covers who it is for, what it filters on, and how results are ordered. The remaining gap is the undocumented limit parameter and the absence of any indication of result shape, which is modest for a tool this simple.

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 50%: state is documented in the schema and the description only repeats that it is required, while limit is undocumented in both places. The ordering rationale implicitly makes limit a top-N control, but the description never states that, so it neither harms nor compensates.

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 resource (the worst-rated bridges in a state) and defines 'worst' concretely as condition = Poor, ordered by lowest component rating then age. That operational definition separates it from generic siblings like search_bridges or list_posted_or_closed_bridges, though it never names those alternatives 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?

The closing sentence gives an explicit trigger ('Use for worst bridges in X questions'), which is clear context for selection. It offers no exclusions or pointer to sibling tools for adjacent questions (e.g., posted/closed bridges), so it stops short of full routing guidance.

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