congress_congressional_record

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

The description states 'Get' which aligns with the readOnlyHint annotation. It does not add behavioral details beyond what annotations provide, such as rate limits or authentication needs, but the annotation already indicates a safe read operation.

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 two short sentences, front-loading the purpose and then covering filter options. No extraneous information, every word 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?

Without an output schema, the description should hint at the return structure. It mentions 'issues' but does not describe fields or pagination. For a filtered retrieval tool, this is minimally adequate but could be improved.

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 input schema has 100% description coverage for all 4 parameters, so the description does not need to add much. It merely restates the filter concept without providing additional meaning or usage examples.

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 the tool retrieves 'Congressional Record issues' and explains it's the official daily record. It uses a specific verb 'Get' and identifies the resource, distinguishing it from other congress tools.

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 tells users to filter by year, month, and day, implying usage context. However, it does not explain when to use this tool versus siblings like 'congress_daily_congressional_record' or 'congress_bound_congressional_record', nor does it mention any prerequisites or exclusions.

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