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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint, covering the read-only and idempotent nature. The description adds value by specifying that PDF download links point directly to the NASA server and are freely accessible without authentication, and by detailing the complete set of fields returned. It does not contradict any annotation.

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 compact two-sentence structure. The first sentence states the core purpose and lists the return fields; the second gives source instructions and the free-access note. Every sentence earns its place, with no fluff or redundancy.

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 is present, so return structure is already defined. The description covers the purpose, how to obtain the ID, and the nature of the data (full record, freely accessible PDFs). For a detail-lookup tool with a single parameter, nothing essential is missing.

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 schema provides a description for the single parameter report_id (e.g., 20140017767), but the tool description adds crucial context on how to obtain that ID: from search/recent results or from the ntrs.nasa.gov/citations/{id} URL. This goes beyond the schema's type definition and helps the agent source the parameter correctly.

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 opens with a specific verb and resource: 'Get the full citation and metadata for a specific NASA technical report by its numeric NTRS ID.' It enumerates the returned fields (title, abstract, authors, etc.) and distinguishes itself from sibling tools by explicitly naming the search and recent tools that supply IDs. This leaves no ambiguity about the tool's function.

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 instructs when to use this tool: to obtain full details once an ID is known, and directs the agent to nasantrs.reports.search or nasantrs.reports.recent for finding IDs, or to extract the ID from the URL. It also notes that PDF links are freely accessible, clarifying authentication requirements. This provides clear context and alternatives.

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