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

No annotations are provided, so the description carries the full burden. It discloses cost, authentication requirements, and return format. It explicitly states it is based on free data and does not invent scores, providing transparency about its limitations. It does not mention potential side effects or rate limits, but as a read-only query, this is minor.

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 relatively concise given the amount of information conveyed (cost, purpose, data sources, limitations, return format). It front-loads key details (PAID, purpose). Minor improvement would be more structured formatting, but overall it is efficient.

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?

Given the tool's complexity (composite of multiple data sources) and the presence of an output schema, the description covers most essential aspects: purpose, cost, data used, what it does not do, authentication, and return fields. It lacks error handling or rate limit info, but these are not critical for selection. It differentiates well among many sibling tools.

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 input schema has 2 required parameters (lat, lon) with 0% description coverage. The description implies lat/lon are coordinates for the site but does not explain units, coordinate system, or valid ranges. While the purpose is clear, the lack of explicit parameter guidance means the agent must infer meaning.

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 assesses a site for reforestation/afforestation using terrain, land cover, and precipitation data. It distinguishes itself from siblings by noting it's a composite for bulk-screening and that it does not invent a 'sequestration score', making its purpose specific and unique among similar assessment tools.

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 mentions cost (100 credits) and that it is priced for bulk-screening convenience, implying use for screening many sites. It also says 'no invented sequestration score', guiding against using it for carbon credit calculations. However, it does not explicitly state when not to use it or name alternatives among siblings.

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