range_doppler_map

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

No annotations. Description only hints at windowing but omits whether this is a destructive operation, if it returns a new object, and what the output represents. Without annotations, the agent lacks behavioral safeguards.

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?

Single sentence, no redundancy, front-loaded with key info. Highly 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?

For a complex tool with 5 parameters and no annotations, the description is too sparse. Output schema exists but missing parameter explanations and usage guidance hurt completeness.

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?

None of the 5 parameters are described; schema provides defaults but no purpose. With 0% schema coverage, the description does not compensate, leaving the agent to guess.

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 specifies the operation ('2D windowed FFT') and the input resource ('RadarCube'), distinct from sibling tools like compute_fft (1D) or render_spectrogram (visualization).

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 usage context: does not state when to use versus alternatives (e.g., compute_fft for 1D), no prerequisites (RadarCube must exist), and no mention of parameters.

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