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

With no annotations provided, the description carries full burden of disclosure. It only states the tool lists future-dated hearings with optional filters, but does not disclose any behavioral traits such as pagination, ordering, rate limits, authentication needs, or what happens if no hearings match.

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 a single concise sentence with parenthetical clarification, which is efficient and front-loaded. However, it lacks structure such as bullet points or explicit parameter breakdowns.

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?

Given 3 optional parameters, no output schema, and no annotations, the description is minimal. It omits important context like return format, pagination behavior, acceptable values for jurisdiction, or ordering. An agent would lack enough information to use the tool correctly without additional documentation.

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 3 parameters (limit, bill_id, jurisdiction), all optional, but schema description coverage is 0%. The description mentions filtering by jurisdiction and bill (which map to bill_id and jurisdiction), but does not explain the 'limit' parameter or provide any additional meaning beyond parameter names. It fails to compensate for the low coverage.

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 verb 'List' and the resource 'upcoming (future-dated) legislative hearings/events, and mentions optional filters by jurisdiction and/or bill. This differentiates it from sibling tools like get_bill_record which focus on bills rather than hearings.

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 provides no explicit guidance on when to use this tool versus alternatives, nor does it mention when not to use it. It merely describes what the tool does without context or exclusions.

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