nightlights_compare

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

No annotations are present. The description does not explain what the tool returns (image, numeric difference?), the area of analysis (point vs. region), or any assumptions (e.g., subtracts radiance). Essential behavioral details are missing.

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 concise sentence with a useful dash-separated elaboration. No superfluous words.

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 4 required parameters, no output schema, and no annotations, the description leaves out critical context like output format (image vs. value), area scope, and comparison method. Incomplete for effective use.

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% with basic parameter descriptions (lat, lng, date format). The tool description adds no extra meaning beyond the schema. Baseline score 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 clearly states the tool compares night light levels between two dates, with specific use cases (power outages, urban growth, conflict damage). It distinguishes from siblings like nightlights_anomaly or nightlights_timeseries.

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 provides use cases but does not explicitly compare with sibling tools or state when to prefer this tool over alternatives. Guidance is implied but not direct.

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