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

Annotations already cover the read-only/idempotent/destructive/openWorld profile, and the description adds substantial context beyond them: the D1 mirror vs NASA Area API fallback behavior, the NASA_FIRMS_MAP_KEY requirement for live mode, pagination support, and the critical semantic caveat that a hotspot is a thermal anomaly and not confirmation of a wildfire.

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?

Four sentences, front-loaded with purpose, then data-source mechanics, then return fields, then the safety caveat and box-size constraint. Every sentence earns its place, especially the return-field enumeration, which compensates for the absent output schema.

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 steps in by enumerating the returned fields (acquisition time, sensor, confidence, FRP, brightness, day/night). Combined with the data-mode/auth and bounding-box constraints, an agent has everything needed to call the tool 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 schema already documents all 11 parameters including the enum values, defaults, and bounds. The description restates some of this (limit/offset pagination, data_mode behavior) but adds little syntax or meaning the schema does not already carry, so the baseline 3 applies.

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 names a specific verb (Search) and resource (NASA FIRMS satellite active-fire/hotspot detections) scoped to a bounded latitude/longitude box. It is unambiguous and no sibling tool overlaps this fire-detection domain, so an agent can route to it confidently.

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?

It gives clear context for use (querying fire detections within a region) and practical guidance such as splitting regions larger than 60x30 degrees into multiple calls. It stops short of explicitly naming alternatives or stating when NOT to use it, but the caveat to verify consequential decisions with incident authorities is a useful usage signal.

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