get_record_versions

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

No annotations are provided, so the description bears full burden. It states the tool returns versions and URLs, which covers basic behavior but omits details like authentication needs, rate limits, or any potential side effects. The behavior is simple and read-only, but the description does not explicitly confirm that.

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 with no extraneous words. Every piece of information (verb, resource, what is returned) is included efficiently.

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 only one parameter and an output schema exists, the description is nearly complete. It could benefit from clarifying the nature of the 'identifier' parameter, but otherwise adequately covers the tool's purpose and return value.

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 single parameter 'identifier' is described only by its name in the schema, with no additional explanation in the description. With 0% schema description coverage, the description should provide clarity on format (e.g., HEPData ID vs DOI) but does not. The parameter is simple but leaves ambiguity.

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 explicitly states the verb 'Return' and the resource 'HEPData record versions', specifying it provides both available versions and version-specific URLs. This clearly distinguishes it from sibling tools like 'get_record' which likely returns a single version or the latest.

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 the tool is for fetching version information but provides no explicit guidance on when to use it versus alternatives. While the context of sibling tools is given, there is no direct instruction on when-not-to-use or prerequisites.

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