Read Specification Resource

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

With no annotations, the description carries the full behavioral burden. It does disclose one useful trait — that an unknown name returns an error listing the available names — and 'Reads' implies a read-only operation, but it omits output format and any confirmation that no state is mutated.

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 short sentences, front-loaded with the core action and followed by the one behavioral caveat. Nothing is redundant and every sentence carries information.

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?

An output schema exists, so return values need not be explained. For a single-parameter read tool this is close to sufficient, with the only real gap being the absence of a full list of valid resource names, which is partially mitigated by the documented error path.

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 0% and the single resource_name parameter has no enum, so the description must supply the value domain. It partially compensates by listing example values ('mode', 'fields', 'all') and noting the error-on-unknown behavior, but does not enumerate the full valid set.

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 states a specific verb and resource ('Reads an ADIF 3.1.7 specification resource') and gives concrete examples ('mode', 'fields', 'all'), so an agent knows exactly what it retrieves. It does not, however, differentiate itself from close siblings like list_enumerations or search_enumerations, which also surface ADIF metadata.

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?

There is no explicit guidance on when to prefer this tool over siblings such as list_enumerations or search_enumerations, nor any stated preconditions. The examples hint at resource names but do not constitute usage direction, so the agent must infer the selection criteria on its own.

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