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

With no annotations, the description carries full responsibility for behavioral disclosure, but it provides none. It does not mention what the tool returns, what units are used, whether it accepts decimal degrees, what happens with invalid coordinates, or any side effects or data source considerations.

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?

While the text is extremely short, it is under-specified rather than concisely informative. 'Elevation: Elevation' conveys almost nothing beyond the tool name and does not earn its place by adding actionable information for an agent.

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?

This is a 2-parameter tool with no annotations and no output schema, so the description is the only source for understanding behavior and expected results. It fails to mention the return value, units, required coordinate system, or failure behavior, making the tool effectively unusable for a correct invocation without outside knowledge.

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%, and both parameters have descriptions ('Lat to process', 'Lon to process'), so the schema already provides basic parameter meaning. The description adds no additional semantic detail such as expected coordinate format, ranges, or required status, so the baseline of 3 is appropriate.

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 is only 'Elevation: Elevation', which tautologically restates the tool name and identifies a resource but never states a verb or action. It does not clearly say that it fetches elevation data for given coordinates, so an agent cannot be certain what the tool actually returns.

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 usage guidance in the description; it never states when to use this tool or how it differs from alternatives. An agent can only infer from the lat/lon parameters that it is intended for coordinate-based elevation lookup, but no explicit usage context or exclusions are provided.

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