Get record comments

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

Barely describes behavior as fetching 'public comments', implying read-only. No annotations exist, so description must cover safety, auth, or limitations, which it does not (e.g., what if naId invalid?).

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?

Single sentence is concise but lacks structure (no paragraphs, no front-loading of key info). Efficient but under-informative.

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?

Tool has no output schema, no annotations, and 3 parameters. Description does not mention return format, pagination, error handling, or comment content. Completely under-specified.

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 coverage is only 33% (naId described). Description adds no parameter details beyond schema, failing to explain limit or page semantics, which is inadequate given low 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?

Clearly states the action ('Fetch public comments') and the resource ('National Archives Identifier'), distinguishing it from sibling tools like get_record_tags.

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?

No guidance on when to use this tool versus alternatives such as search_records or get_record_tags. Missing context for appropriate use.

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