govinfo_get_package

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

Annotations already indicate readOnlyHint and openWorldHint. The description adds: response structure with found:true/false, package object, and meta; that a nonexistent packageId returns found:false with HTTP 404; and that API keys in download links are stripped. This provides full transparency 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?

The description is concise (three sentences) and front-loaded with the core action. Every sentence adds information: what it does, how to use it, and important edge-case behavior. No wasted words.

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?

For a simple fetch tool with one parameter and no output schema, the description is complete. It covers the response structure, error handling (404), and data cleaning (API key stripping). No further details are needed for correct invocation and understanding of results.

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 100% with a description for packageId. The tool description adds value by explaining the source of the ID (from govinfo_search_packages) and providing examples, which helps the agent understand the expected format. This goes beyond the schema's minimal description.

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 it fetches a single GovInfo package's summary with metadata and download links. It specifies the required packageId and gives concrete examples. It distinguishes itself from sibling tool govinfo_search_packages by indicating that its input comes from that search.

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 usage: after obtaining a packageId from govinfo_search_packages. It does not explicitly state when not to use it or mention alternatives, but for a fetch tool this is reasonably clear. The behavior on nonexistent ID (404) is explained.

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