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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint=false, and destructiveHint=false, covering the safety profile. The description adds no behavioral context such as freshness/liveness of hotspots, geospatial query semantics, rate limits, or return behavior beyond the annotations.

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?

The description is a single compact sentence with no padding. It is front-loaded with the data types, though it is a noun-phrase fragment rather than a structured statement of action and usage.

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 sensor tool with a completely opaque 'input' parameter, no output schema, and closely related sibling tools, the description is too thin. It leaves an agent unable to determine the actual input format, return shape, or when this tool should be selected over cell_sensor_wildfire or cell_sensor_wildfire_perimeter.

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 0% and the single required parameter is an untyped 'input' object. The description hints that input may encode a point, box, or active wildfire query, but gives no syntax, shape, or examples to make the opaque parameter usable.

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 specific data types (active wildfires, burn perimeter, satellite hotspots), so the resource is identifiable. However, it gives no verb and does not distinguish this tool from the sibling tools cell_sensor_wildfire and cell_sensor_wildfire_perimeter, which appear to overlap directly.

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 implies three query modes ('near a point', 'in a box') but never states when to use this tool instead of the related wildfire/perimeter siblings. There are no exclusions, prerequisites, or alternative routing guidance.

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