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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful behavioral context: results are advisory rule text rather than calculations, each rule comes with its citation, and coverage is strictly federal (no state rules) — which prevents misreading a thin result.

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?

Purpose and scope are front-loaded in the opening clause, with the topic list functioning as a coverage manifest. The colon-separated enumeration is long but each item maps to a real rule an agent might be looking for, and the trailing 'Federal only' closes the scope cleanly.

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?

No output schema exists, so the description should do more to set expectations about the shape of the response (e.g., list of rules per topic vs. a single verdict). It covers scope and citations well but leaves the return structure and the handling of omitted/unknown inputs (like weight) unaddressed.

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 60%, so some parameters are documented inline. The description reinforces key semantics — organization types map to the enum, 15-passenger vans relate to the passengers input, and 'new vehicles only' explains the new_vehicle flag — but it never mentions carries_students or weight_over_26000_lb, leaving those to 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 concrete verb+resource (returns US federal rules and guidance with citations) and enumerates the rule topics covered, so an agent can tell it apart from narrow siblings like find_skoolie_bus or get_bus. It does not explicitly distinguish itself from check_cdl_requirement, which appears to be a subset of what this tool covers.

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 framing 'buying a bus' plus 'Federal only' implies when it applies (federal compliance research, not state/local), but there is no explicit when-to-use or when-not-to-use guidance and no routing to alternatives such as check_cdl_requirement or get_buying_context.

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