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

With no annotations, the description carries the transparency burden. It usefully discloses output components (trade/filing counts, buy/sell split, volume range, coldpine.io page), but it does not state whether this is read-only, how limit affects results, or behavior for no matches. These gaps prevent a fully transparent picture.

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 first states purpose and matching mode, the second lists return values. Every word contributes, and there is no repetition of schema/defaults.

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 3-param search tool with no output schema or annotations, the description is adequate but incomplete. It explains main outputs and the name-search use case, but it lacks explicit alternative routing, limit behavior, and a fuller return-shape description, so an agent may still be unsure about edge cases.

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 only 33%, so the description needs to compensate. It clarifies that query is a partial name and hints at chamber via 'House or Senate', but it says nothing about limit's semantics beyond the schema's default/max. The description adds some meaning but does not fully cover the undocumented parameters.

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 names a specific action ('Find members ... by (partial) name'), a precise resource (U.S. House or Senate members with disclosed stock trades), and the returned data. This differentiates it from singular 'get_member' and other sibling tools, so an agent can recognize what it does without opening the schema.

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 intended use is implied: search by partial name when you need a member's trade/filing summary. But there is no explicit when-to-use/when-not-to-use guidance or mention of alternatives like get_member for exact member lookup, so the agent must infer routing.

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