midnight-get-file-at-version

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint, so the description does not need to restate these. The description adds context about ensuring recommendations match the user's version, which is helpful but does not disclose potential failure modes, caching, or version resolution details. Minimal addition beyond 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?

Three sentences: purpose, critical note, and preference directive. Every sentence adds distinct value, and the purpose is front-loaded. No wasted words or repetition.

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?

The description covers the core purpose and usage context but lacks details about the return format, error behavior (e.g., version not found), and edge cases. Given no output schema, additional output description would improve completeness. Annotations partially compensate for safety 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?

Input schema covers all three parameters with descriptions (100% coverage). The tool description does not add any parameter-specific meaning beyond the schema. According to guidelines, baseline is 3 for high coverage, and no extra value is provided.

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 gets the exact content of a file at a specific version, and explicitly distinguishes it from the sibling 'midnight-get-file' by emphasizing version accuracy. The verb 'get' and resource 'file at a version' are specific, and the critical note reinforces the unique value.

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 explicitly says to prefer this over 'get-file' when version accuracy matters, providing clear guidance on when to use this tool. It does not explicitly state when not to use it, but the preference directive implies alternatives. Could be more comprehensive with exclusion criteria.

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