compare

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does not state whether the operation is read-only, what happens if no measurement or target exists, or how 'latest' is determined. It only lists output content, omitting side effects, dependencies, and potential error conditions.

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, front-loaded sentence that efficiently conveys purpose and outputs. It is concise and readable, though the list of outputs could be more structured for even quicker scanning. Overall, it is appropriately sized with no waste.

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 description covers the core behavior and default case, and an output schema exists to document return structure. However, it lacks information on preconditions (e.g., a target must be set) and error handling. For a simple tool with one optional parameter, this is mostly complete, but the missing preconditions and failure modes are notable gaps.

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 schema has 0% description coverage, so the description must compensate. It explains that the optional measurement_id defaults to null and that null means the latest measurement, which is not evident from the schema alone. This adds meaningful context for the only parameter, covering it well.

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 clearly states the action (compare a measurement with the target) and specifies the exact outputs: per-axis gaps to the acceptance band, 20-320Hz curve error per band, and plain-word explanations. It distinguishes itself from related sibling tools by focusing on comparing to a target rather than measuring or monitoring.

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?

The description does not mention when to use this tool versus alternatives like 'verify', 'monitor', or 'measure'. It explains the default behavior (latest measurement) but provides no guidance on selection criteria or exclusions, leaving the agent to infer appropriate usage from sibling names.

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