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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false. The description adds genuinely useful behavioral context beyond those hints: the data is public-domain, submitted by pilots/controllers, the default no-arg behavior returns multiple aggregate views, and state values must be lowercase hyphenated slugs. It does not discuss volume or edge cases, but the output schema likely covers return structure.

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?

Two sentences carry all the essential information with no filler. The resource and source are front-loaded, and the conditional behavior is stated compactly with the slug-format constraint included.

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 tool with one optional parameter, full schema description coverage, safety annotations, and an output schema, the description covers everything needed for correct invocation: no-arg behavior, per-state behavior, and the expected state format. There is no apparent missing operational information.

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 schema already documents the single state parameter at 100% coverage as a 'US state slug for a per-state breakdown.' The description adds the specific lowercase-hyphenated format requirement and clarifies that the parameter is optional and switches the response into state-level mode, which is more than the schema alone provides. This justifies a score above the baseline 3.

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?

The description identifies a specific resource (FAA UAS/drone sighting reports), names the data source, and explains both invocation modes: no-arg gives national totals/yearly series/leading states and cities, while a state argument gives a per-state breakdown. This is unambiguous and naturally distinguishes the tool from the accident/laser/wildlife-strike siblings, even without explicit contrast.

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 description gives clear usage context: call with no arguments for national aggregate data, or pass a state slug for a state-level breakdown. It does not explicitly list exclusions or alternatives, but the modes are concrete enough that an agent knows how to choose between them.

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