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

With no annotations, the description carries the full burden and does substantial work: it discloses the silent-failure mode ("A name that does not match returns count 0 and no error"), the name-normalization rule (honorifics stripped, often a legal name), and the single-spelling limitation. It does not cover auth requirements, rate limits, or what happens at the limit boundary, so it falls short of full behavioral disclosure.

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?

Three sentences, all front-loaded: capability and ordering first, then the critical name-matching constraint, then the escape hatch to the sibling. Every clause carries operational information an agent needs, and none restates the name or title.

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?

There is no output schema, yet the description never describes the shape of a returned trade record (fields, count semantics beyond the failure case), leaving the agent to infer it. Everything else an agent needs to call the tool correctly — name resolution, filtering, ordering, empty-result behavior — is present.

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 description coverage is 100%, so the schema already documents all four parameters, and the baseline is 3. The description adds real meaning for member_name by explaining how the stored spelling is derived and why an exact match matters, but adds nothing new for days, limit, or ticker beyond what the schema states.

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 and resource ("Returns stock trades disclosed by one member of Congress"), plus ordering (newest first) and the optional filters. It also distinguishes itself from the two siblings an agent would most likely confuse it with, search_members_and_tickers and get_trade_feed.

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?

Gives explicit preconditions ("resolve a common or partial name with search_members_and_tickers first") and an explicit alternative for the edge case where a member filed under multiple spellings ("use get_trade_feed with a partial name"). When-to-use and when-to-use-something-else are both spelled out.

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