vna_marker_search_max

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

With no annotations, the description carries the full responsibility for behavioral disclosure. It only states the action of searching for a maximum value but does not describe side effects (e.g., moving a marker), requirements (e.g., existing marker), or return behavior.

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 lacking any structural detail. While concise, it is under-specified similar to the 'Process' example, failing to convey important context in an efficiently structured way.

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?

The tool has no annotations, no output schema, and a minimal description. It does not explain what 'search' entails (e.g., frequency/amplitude), how the search is initiated, or what the return value is. Given the presence of many sibling tools, more context is needed for appropriate selection.

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 only 33% (only marker_num has a description). The description adds no parameter explanation for host, port, or marker_num, and does not compensate for the missing schema documentation. No semantic value is added beyond the schema.

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 'Search for maximum value in sweep' states a specific verb and resource, and the word 'maximum' distinguishes from sibling tool vna_marker_search_min. However, it is vague about what exactly is being searched (e.g., marker maximum) and lacks detail on the context.

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 on when to use this tool versus alternatives like vna_marker_search_min or vna_set_marker. No prerequisites or use cases are mentioned.

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