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

Beyond the readOnly/openWorld/destructive annotations, the description discloses two non-obvious behavioral traits: the GAOREPORTS collection is a stale historical archive (~16.5K reports, no recent updates) and v1A returns metadata only with the full body at package_link. Both would materially change how an agent answers if omitted.

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?

Front-loaded purpose sentence followed by clearly headed bullets, collections block, and pairing patterns — every section is scannable. It is however quite long (~350 words) and some collection prose is richer than strictly needed for selection.

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?

With no output schema, the description carries the return-value burden and does so by stating that only metadata is returned and that content lives at package_link. Combined with full collection coverage, usage triggers, and identifier format, an agent has everything needed to call it correctly.

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% so the baseline is 3, but the description adds genuine meaning: each `collection` enum value is given interpretive significance (CRPT as a real-time floor signal, PLAW as the 'what actually got done' record, CHRG as a precursor to enforcement), and the package_id naming convention is decoded with worked examples. The remaining date/sort/limit params are left to the schema.

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?

States a specific verb+resource (returns recent congressional + oversight publications from GovInfo) and names the exact four collections it spans. An agent can distinguish it from get_bills, get_roll_call_votes, or get_federal_register_documents from the description alone.

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?

Opens with an explicit 'Use this when the user asks about' block enumerating four triggering scenarios (committee reports, signed public laws, hearing transcripts, GAO oversight). It also routes to alternatives via named cross-source pairing patterns (get_congressional_trades, get_enforcement_actions, get_bills + get_roll_call_votes) with the condition that selects each.

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