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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. The description only gives the output format (elevation in metres) but says nothing about input requirements, error handling, rate limits, or any side effects. It does not state whether the tool is read-only, but since it reports elevation, it is likely safe; however, the description itself does not confirm this.

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 sentence and front-loads the purpose, but it repeats the tool name 'Elevation:' without adding value. It is concise but at the expense of necessary details. The structure is acceptable, but the redundancy slightly lowers the score.

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?

Although an output schema exists and parameter count is low, the single parameter 'q' is completely unexplained. The description gives no context about what query is expected or whether the tool can work without a value. For a tool with only one parameter, this is a significant gap that an agent would struggle to resolve.

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 one parameter 'q' with no description, and schema description coverage is 0%. The description does not mention 'q' at all, providing no hint about what value should be passed (e.g., latitude/longitude, place name, or something else). This is a critical omission because the agent cannot determine how to invoke the tool correctly.

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 states 'Ground elevation in metres' which clearly identifies the resource (elevation) and units (metres), and names the data source (Open-Meteo). It is not a tautology because it adds the unit and source beyond the tool name. However, it does not explicitly state that the tool returns this for a location, nor does it distinguish itself from potential sibling tools like geocode or revgeocode, though no direct sibling exists.

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?

There is no guidance on when to use this tool versus alternatives, and no mention of what kind of input (e.g., coordinates, place name) is needed. The description only states what the tool provides, not when the agent should select it. This is a gap for a tool with a generic parameter name 'q'.

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