congress_treaties

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

The readOnlyHint annotation already covers the safe read-only nature, and the description adds useful scope and output-field context (topic, date transmitted, ratification status). However, it does not disclose pagination behavior, response format, or any rate limits, so the added transparency beyond annotations is moderate.

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-loaded with the primary action ('List treaties submitted to the Senate') and then the key output fields. Every word earns its place, and there is no redundant 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 simple list tool with four well-documented parameters and a read-only annotation, the description covers purpose and output fields adequately. It could be more complete by mentioning pagination or the default limit, but the schema covers limits, and the tool is not highly complex, so a score of 4 is justified.

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% and all four parameters (limit, congress, toDateTime, fromDateTime) already have descriptive text. The tool description adds no additional parameter-level meaning beyond clarifying the output fields, so the baseline 3 is appropriate.

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 uses a specific verb ('List') with a clear resource ('treaties submitted to the Senate') and scope ('submitted to the Senate'). It also names the displayed fields (topic, date transmitted, ratification status), distinguishing this list tool from sibling tools like congress_treaty_details or congress_treaty_full_profile.

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 clearly implies use for retrieving a list of treaties, but provides no explicit when-to-use vs. alternatives or when-not-to-use guidance. Sibling tool names like congress_treaty_details suggest alternatives, but the description itself does not mention them or any exclusions.

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