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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true. The description adds important behavioral context: a sitting can run to 850,000 characters and the tool returns a window using offset, max_chars, and next_offset, or search passages. It does not mention rate limits or the schema's 20-passage search cap.

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 front-loaded with the purpose, then explains transcript size and window/search behavior, then ends with the prerequisite for obtaining transcript_id. Every sentence earns its place with no filler.

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 read-only transcript retriever with full schema descriptions and annotations, the description covers purpose, scale, pagination, search behavior, and ID sourcing. Because there is no output schema, it could say more about the structure of returned passages, but it is largely complete.

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 all four parameters are already documented. The description adds practical meaning by framing offset/max_chars as a window and by giving a concrete use for search, such as a bill number or member's name, though it does not add syntax detail for transcript_id.

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 gives a specific verb and resource: the verbatim record of one chamber sitting, covering debate, explanations of vote, and roll calls. It clearly distinguishes this from the listing sibling by saying to get transcript_id from list_floor_transcripts.

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?

It tells the agent to obtain transcript_id from list_floor_transcripts and explains when to use the search mode versus reading a window. It stops short of explicit when-not-to-use guidance or naming other alternatives beyond the listing tool.

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