congress_bound_congressional_record

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

Annotations already declare readOnlyHint=true, so the description aligns. It adds minimal context beyond 'Get' and filtering, but does not disclose pagination, rate limits, or data format. With annotations present, the bar is lower, but value added is limited.

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?

Two sentences, zero wasted words. Front-loads the core verb and resource, then briefly lists filters. Excellent structure for quick comprehension.

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 tool with 4 optional parameters and no output schema, the description fails to explain what the output contains (e.g., list of issues with metadata). It does not mention defaults or limitations, leaving the agent guessing about the return format.

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 100%, so baseline is 3. The description only repeats that params exist for filtering, adding no additional semantics beyond the schema's descriptions of year, month, day, and limit.

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 explicitly states 'Get bound Congressional Record issues' with a clear verb and resource. It distinguishes from siblings like congress_daily_congressional_record by noting it's the 'permanent, final publication.'

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 mentions filtering by year, month, and day but provides no guidance on when to use this tool versus alternatives like congress_congressional_record or congress_daily_congressional_record. No exclusions or use cases are given.

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