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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds the normalization attribute, but omits behavioral context that matters here: the ticker parameter is deprecated and returns a validation error (only disclosed in the schema), House requires member, and Senate has incompatibility rules. These are disclosed in parameter descriptions, not the prose, so the description adds little beyond annotations.

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 tight sentences; the resource and scope are front-loaded and the alternative routing follows immediately. 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?

An output schema exists, so return values need not be explained. Combined with annotations, the description covers purpose and the search/detail split adequately. It could add one sentence noting the House-vs-Senate parameter incompatibilities given the 17-param surface, 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 the schema already documents all 17 params, including the deprecated ticker, page cap, and incompatibility notes. The description itself adds no parameter-level detail. Baseline 3 is appropriate when the schema does the heavy lifting.

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?

States a specific verb (Search) and resource (normalized public House and Senate stock-disclosure filing rows), with 'normalized' hinting at the distinction from raw filings. However, it does not differentiate from other finance/disclosure siblings like sec_insider or sec_institutional_holdings, which an agent might reasonably confuse it with.

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?

Explicitly routes the agent to the sibling tool congress_report 'when you need one disclosure's detail.' That is a clear search-vs-detail guideline. However no when-not guidance beyond that single alternative, e.g. nothing about chamber choice or House-vs-Senate pitfalls.

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