hamqth_verify_qso

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

Discloses that the tool is public and requires no authentication, and that it checks QSO existence for both parties. No side effects or rate limits mentioned, but the operation is simple and read-only, so transparency is adequate.

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?

Two focused sentences with no redundant information; efficient and front-loaded with core purpose.

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?

Given no annotations, the description covers purpose, authentication status, and database scope. The output schema exists and is not required in description. Adequate for a simple verification 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?

All 4 parameters are documented in the input schema with clear descriptions; the description adds no additional semantic detail beyond referencing the protocol (SAVP), so no extra value beyond schema coverage.

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 specifies the action 'verify a QSO' and the resource 'HamQTH database', distinguishing it from sibling tools like hamqth_lookup or hamqth_dxcc which serve different purposes.

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 explicit guidance on when to use this tool versus alternatives; no exclusions or prerequisites mentioned beyond stating it's public and requires no auth.

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