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

No annotations are present, so the description carries the full burden of explaining behavior, and it provides none. It does not state what the tool returns, what units are used, whether it is deterministic, or whether it has side effects. The text only repeats the name.

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 very short, but the brevity is the result of under-specification rather than efficient writing. It repeats the tool name and title without offering any additional structure, context, or useful detail.

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 no output schema, no annotations, and no parameter guidance, this description is effectively the only source of context, and it explains almost nothing. An agent cannot determine what output to expect, what units are involved, or what doppler refers to in this tool. The definition is incomplete even for a no-parameter tool.

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 tool has zero parameters, so the empty schema fully documents the inputs and there is no parameter ambiguity to resolve. The baseline of 4 applies because no parameter semantics are missing.

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 a direct restatement of the tool name: Doppler Frequency: Frequency of doppler. It lacks a verb and does not specify what quantity is computed, what inputs influence it, or what the result represents. This reads as a tautology rather than an informative purpose statement.

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?

No guidance is provided for when to invoke this tool or how it differs from alternatives such as x402-frequency, x402-wave-speed, or x402-velocity. The description gives no scenario, prerequisite, or exclusion information.

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