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

No annotations are provided, so the description bears full burden. It discloses that the tool requires no key and returns specific JSON fields, but lacks information on side effects, rate limits, or whether it is read-only (likely safe). This is minimal but sufficient for a simple query tool.

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 brief, with two well-organized sentences. It front-loads the purpose and lists outputs in a structured list. Every sentence is meaningful, though some could be more explicit.

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 0% schema coverage and no annotations, the description is adequate for a simple tool with two numeric parameters. It lists output fields, but could improve by specifying coordinate system or edge cases (e.g., invalid coordinates).

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 coverage is 0%, so description must compensate. It implies parameters are coordinates but does not specify expected format (e.g., WGS84) or valid ranges. This adds minimal value over the schema's type definitions.

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's purpose: assessing EV charging sites by combining grid proximity, land cover, and locality context. It uses specific verb 'scouting' and resource 'EV charging site', and distinguishes from sibling tools like 'assess_renewable_site' by focusing on EV.

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 implies usage for EV site scouting and mentions 'No key needed' indicating easy access. However, it does not provide explicit when-to-use or when-not-to-use guidance, nor does it 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.