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

With no annotations provided, the description carries the burden of establishing the operation's profile. It does so by framing it as a read-only analytical query ('Returns...') and by giving the output fields, so an agent can see it is non-mutating. It does not mention ordering or the exact clustering threshold, but no side effects or hidden mutations are implied.

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 dense sentences plus a source reference, with no filler. The core definition is front-loaded, and the returned fields are listed concisely. Every sentence adds useful information.

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 4-parameter tool with no output schema and no annotations, the description is reasonably complete but has gaps. It states the query concept, the output fields, and the data source, but it does not explain how `limit`, `min_members`, and `window_days` interact, nor what ordering the results use. These missing details matter because neither the schema nor annotations supply them.

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 0%, so the description must compensate for parameter meaning. It partially does: 'same direction' maps to `direction`, 'rolling window' maps to `window_days`, and 'several members' maps to `min_members`. However, `limit` is never mentioned, and the parameter mappings are vague enough that an agent could not confidently set exact values without inspecting 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 opens with a specific and non-tautological definition: 'Stocks that several members of Congress traded in the same direction inside a rolling window,' then enumerates the exact returned fields. This clearly differentiates it from sibling listing/filing tools such as list_transactions and search_members.

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 implies the use case—finding correlated congressional trades—but never states when to prefer this tool over siblings or when not to use it. The references to 'the bot' and the coldpine.io page provide context but no explicit alternative routing or exclusion criteria.

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