light_pollution_map

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

The description mentions the return type (grid of data points) but does not disclose other behavioral aspects like rate limits, required permissions, or read-only nature. Since no annotations exist, the description should provide more context.

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 succinct, with a clear purpose sentence followed by parameter explanations. No superfluous content.

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?

The description covers all parameters and indicates the output data types. With an output schema present, it does not need to detail return structure further. Minor omission: coordinate system not specified.

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 description explains the bounding box parameters and the zoom default, compensating for the 0% schema description coverage. It adds meaning beyond the schema by stating 'Bounding box coordinates' and the effect of higher zoom.

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 gets light pollution data for an area and lists the data points (brightness, Bortle class, SQM). It is distinct from sibling tools which focus on celestial positions, weather, etc.

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 does not provide explicit guidance on when to use this tool versus alternatives. It only states what it does, leaving the agent to infer usage context.

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