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

With no annotations provided, the description carries the full burden and does so effectively. It discloses key behavioral traits: public access, no authentication required, and caching behavior with refresh frequency. This covers safety, access, and performance aspects, though it could add more on error handling or rate limits for a higher score.

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 front-loaded with the core purpose, followed by supporting details in two concise sentences. Every sentence adds value: the first defines the tool's function, and the second covers access and data behavior, with no wasted words.

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's low complexity (single parameter, no nested objects), the presence of an output schema (which handles return values), and the description's coverage of key behavioral aspects, it is complete enough for effective use. The description addresses access, data source, and caching without redundancy.

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 input schema has 100% description coverage, clearly documenting the single 'callsign' parameter. The description adds no additional parameter details beyond what the schema provides, such as format examples or constraints. Baseline 3 is appropriate as the schema handles the heavy lifting.

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 specific action ('Check') and resource ('Authenticity Guaranteed (AG) status on eQSL'), with the callsign as the target. It distinguishes from siblings like 'eqsl_download' or 'eqsl_inbox' by focusing on AG status verification rather than file operations or inbox management.

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 provides clear context for usage ('Public, no auth required') and mentions the data source ('cached copy of the AG member list, refreshed every 4 hours'), which helps determine when to use it. However, it does not explicitly state when to use alternatives like 'eqsl_verify' or exclude specific scenarios, keeping it from a perfect score.

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

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

With no annotations provided, the description carries the full burden. It discloses the tool's behavior by stating it returns '.adi file content' and instructs to 'save to disk for import into your logger', which adds useful context about output handling. However, it doesn't mention potential side effects, authentication requirements, rate limits, or error conditions that would be important for a download operation.

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 perfectly concise with three sentences that each earn their place: the first states the core purpose, the second explains the return value and usage, and the third provides important guidance about the 'since' parameter. No wasted words, and the most critical information appears first.

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 that there's an output schema (which handles return value documentation) and 100% schema coverage for parameters, the description provides adequate context for this download operation. It explains what the tool does, what it returns, and key usage guidance. The main gap is the lack of behavioral details like authentication or error handling, but with output schema covering return values, this is reasonably complete.

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 the schema already documents all three parameters thoroughly. The description adds minimal value beyond the schema by mentioning the 'since' parameter's optional nature ('Omit for full history'), but doesn't provide additional semantic context about parameters like 'persona' or 'qth_nickname'. This meets the baseline for high 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 states the specific action ('Download your complete eQSL inbox') and the resource ('as raw ADIF text'), distinguishing it from sibling tools like eqsl_inbox (which likely shows inbox contents) and eqsl_ag_check/eqsl_last_upload/eqsl_verify (which perform different eQSL-related actions). The verb 'download' is precise and the output format is explicitly mentioned.

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 provides clear context for when to use the tool ('download your complete eQSL inbox') and includes a specific usage note about omitting 'since' for full history. However, it doesn't explicitly contrast when to use this tool versus its siblings (like eqsl_inbox), which would be needed for a perfect score.

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

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

No annotations are provided, so the description carries full burden. It states the tool downloads data but doesn't disclose behavioral aspects like authentication requirements, rate limits, output format, pagination, or whether it's a read-only operation. The description is minimal and lacks critical operational context.

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 with zero wasted words. It's front-loaded with the core purpose and uses parentheses to add clarifying context without bloating the text.

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 5 parameters, no annotations, but 100% schema coverage and an output schema exists, the description is minimally adequate. It covers the basic purpose but lacks behavioral transparency and usage guidance that would be helpful for an AI agent, especially without annotations.

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 the schema fully documents all 5 parameters. The description adds no parameter-specific information beyond implying date filtering via 'incoming eQSLs', which aligns with the 'since' parameter. Baseline 3 is appropriate when schema does the heavy lifting.

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 ('Download') and resource ('incoming eQSLs') with specific scope ('confirmations others have sent you'). It distinguishes from siblings by focusing on incoming confirmations rather than uploads, verification, or AG checks, though it doesn't explicitly name alternatives.

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 retrieving confirmations sent to you, but provides no explicit guidance on when to use this tool versus alternatives like eqsl_download or eqsl_verify. No prerequisites, exclusions, or comparative context are mentioned.

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

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool checks a timestamp ('when...last uploaded'), implying a read-only operation, but doesn't clarify if it requires authentication, has rate limits, or what happens if the persona doesn't exist. For a tool with no annotation coverage, this leaves significant gaps in understanding its 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, clear sentence that efficiently conveys the tool's purpose without unnecessary words. It's front-loaded with the core action ('Check when...'), making it easy to understand at a glance. Every part of the sentence earns its place by specifying key details.

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's low complexity (one parameter, no nested objects) and the presence of an output schema (which handles return values), the description is reasonably complete. It covers the basic purpose and parameter context, though it could benefit from more behavioral details given the lack of annotations. For a simple lookup tool, this is adequate but not exhaustive.

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 input schema has 100% description coverage, with the single parameter 'persona' documented as 'Persona name configured in adif-mcp.' The description doesn't add meaning beyond this, such as examples or constraints on persona names. Since the schema does the heavy lifting, the baseline score of 3 is appropriate.

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 when a persona last uploaded QSOs to eQSL.' It specifies the verb ('check'), resource ('last uploaded QSOs'), and target system ('eQSL'). However, it doesn't explicitly differentiate from sibling tools like 'eqsl_verify' or 'eqsl_inbox', which might also involve checking eQSL status, so it doesn't reach the highest score.

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 provides no guidance on when to use this tool versus alternatives. It doesn't mention sibling tools or contexts where this specific check is appropriate, such as monitoring upload frequency or troubleshooting sync issues. Without such guidance, users might struggle to choose between this and tools like 'eqsl_verify'.

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

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.