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

Annotations already establish that this is a safe, read-only, open-world operation. The description adds useful context about the wildfire data types returned, but it does not explain query behavior, return format, or how the point/box modes behave.

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 filler. It is front-loaded with the data categories, though the lack of an action verb slightly weakens the structure.

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 an opaque input parameter, no output schema, and multiple closely related wildfire siblings, the description is not complete enough to tell an agent how to call the tool correctly. It needs at least basic input-shape or sibling-routing guidance.

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 single parameter is named only 'input' with no type, structure, or description, and schema coverage is 0%. The description hints at point-based and box-based queries, but it does not explain how to encode either mode, leaving the parameter effectively undocumented.

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 the wildfire data types covered, including active wildfires, burn perimeter near a point, and satellite hotspots in a box. However, it is a noun phrase without a clear verb and does not distinguish this tool from sibling tools such as cell_sensor_wildfire or cell_sensor_wildfire_hotspots.

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 lists possible data categories but gives no guidance on when to use this tool versus the wildfire or hotspots siblings. It does not state prerequisites, exclusions, or alternative tools.

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