eqsl_verify

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

With no annotations provided, the description carries full burden. It discloses key behavioral traits: it's a read operation ('check'), requires no authentication ('no auth required'), and is publicly accessible ('public'). This covers safety and access, though it doesn't mention rate limits, error handling, or response format, which are gaps for a tool with no annotations.

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, efficient sentence that front-loads the core purpose ('Check if a specific QSO exists in eQSL') and adds essential context ('public, no auth required'). There is no wasted text, and it's appropriately sized for the tool's complexity.

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 the tool has an output schema (implying return values are documented), no annotations, and high schema coverage, the description is reasonably complete. It covers purpose, access, and authentication, but lacks details on behavioral aspects like rate limits or error cases, which are minor gaps in an otherwise adequate context.

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 100%, so parameters are well-documented in the schema. The description adds no specific parameter semantics beyond implying the tool checks QSO existence based on inputs like callsigns and date. This meets the baseline of 3 since the schema handles parameter details, but the description doesn't enhance understanding of how parameters interact.

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 tool's purpose: 'Check if a specific QSO exists in eQSL' with the verb 'check' and resource 'QSO in eQSL'. It distinguishes from siblings by specifying it's for verification (vs. download, inbox, etc.), though it doesn't explicitly name alternatives. The 'public, no auth required' adds context but doesn't fully differentiate from all siblings.

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 implies usage for verifying QSO existence, and 'public, no auth required' suggests when authentication isn't needed. However, it doesn't explicitly state when to use this vs. alternatives like 'eqsl_ag_check' or 'eqsl_download', nor provide exclusions or prerequisites beyond the implied verification context.

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