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

Annotations already declare this is a read-only, idempotent, non-destructive, closed-world query, so the safety bar is low. The description goes beyond that by defining what 'flagged' actually means (over the federal intervention threshold), naming the five BASIC categories, and disclosing the population size (~1,526 carriers) and the out-of-service inspection count in the payload.

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?

Front-loaded with the definition of the result set, then return fields, then population size, then filters. Dense and mostly waste-free, though the enumerations of BASIC categories and returned fields are somewhat list-heavy.

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, the description correctly compensates by naming the returned fields (name, location, fleet size, flagged BASICs, out-of-service counts). It also conveys result scale. The only unaddressed behavior, pagination via limit, is fully documented in the schema, so an agent has enough to call this 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?

Schema description coverage is 100%, so the baseline is 3. The description nudges above baseline by spelling out the five BASIC categories in human-readable form, which helps an agent connect the opaque codes (unsafe_driv, hos_driv, etc.) in the schema to their real meaning.

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?

Opens with a specific verb+resource+scope: FMCSA motor carriers flagged above the federal intervention threshold in SMS BASIC categories. This is precise enough that an agent can distinguish it from adjacent tools like company_risk_flags or fed_enforcement_recent without opening any schema.

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 final sentence implies usage by listing the three filter dimensions (state, BASIC, min alert count), which tells an agent how to narrow results. However, it gives no explicit when-to-use versus when-not, no prerequisites, and never names an alternative tool for carrier lookups, so usage remains inferred rather than stated.

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