Congressional Research and Professional - CRS reports and Congress analytics

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

With no annotations provided, the description carries the full burden of behavioral disclosure, but it only offers vague claims like 'professional-grade research data with enhanced analytics and historical insights.' It does not explain operation-dispatch behavior, required parameters, permissions, rate limits, or output characteristics.

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 bulleted structure is readable and helps organize the six operations, but the opening line largely repeats the title, and the closing 'Returns professional-grade research data...' is filler. It is reasonably compact but not every sentence earns its place.

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?

This is a complex multi-operation dispatcher with 10 parameters and no operation enum in the schema, so the description should clarify operation routing and per-operation parameter usage. It lists sub-operation names but lacks enough context to reliably invoke the tool, especially since schema coverage is 0% and no annotations are provided.

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 description coverage is 0%, so the description must compensate, but it only lists 'Key params: operation, congress, keywords, report_number, start_year, end_year' without explaining their meanings or which params apply to which operation. Params like limit, current, detailed, and format_type are entirely unexplained.

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 provides 'CRS reports and enhanced Congress analytics' and enumerates six specific sub-operations with one-line explanations. This distinguishes it from sibling tools focused on bills, members, committees, and laws, though the tool itself is a broad dispatcher rather than a single focused operation.

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 grouped bullet list gives context for which operation to use within the tool (e.g., 'get_congress_info - Basic' vs 'get_congress_info_enhanced - Advanced analytics'), implying usage based on desired depth. However, there is no explicit guidance about when to prefer this tool over siblings or when not to use it.

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