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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states 'Search' which is already in the tool name, and offers no information about result format, pagination, rate limits, or any access requirements. The phrase 'Track...' could imply ongoing monitoring rather than a one-time search, which is potentially misleading.

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 short sentences, immediately stating the purpose and a use case. There is no filler or redundant information, making it easy to parse.

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 search tool with only 2 parameters and no output schema, the description gives the core purpose and a relevant use case. However, it lacks detail about what results look like, any default behavior (e.g., query required), or limitations, which is a notable gap given the absence of an output schema.

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 covers 100% of the parameters with descriptions, so the baseline is 3. The description adds example topics like 'stablecoin' and 'digital asset' which indirectly enrich the query parameter, but it does not provide any additional parameter-level detail beyond the schema.

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 'Search US Congressional bills', which is a specific verb and resource. It distinguishes from sibling tools like court_opinion_search, eurlex_search, and uk_legislation_search by identifying US Congressional bills as the target. Adding 'stablecoin, crypto, financial regulation bills' further narrows the use case.

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 second sentence 'Track stablecoin, crypto, financial regulation bills' provides clear context for when the tool is relevant. However, it does not explicitly state when not to use it or mention alternative tools, so it stops short of a full usage guideline.

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