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

With no annotations provided, the description carries the full burden of behavioral disclosure. It thoroughly lists what the tool returns, which is transparent about output, but it does not mention any side effects, limitations (e.g., valid ticker requirements, empty results), or performance characteristics. It is a read-only query by nature, but that is not explicitly stated, so the disclosure is adequate but not rich.

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?

The description is a single long run-on sentence that packs many output components. While it is front-loaded with the core purpose, the listing is cumbersome and would benefit from bullet points or separate sentences. It is not concise, but it contains no filler; every clause adds information, so it is not overly verbose.

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?

The description lists all expected return items in detail, which is sufficient for an agent to know what to expect. It does not mention error conditions or how to handle missing data, but given the simple one-parameter interface and the absence of an output schema, it covers the essential information an agent needs to call the tool correctly.

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 has 100% coverage for the single parameter 'ticker' with a description 'Stock symbol, e.g. NVDA.' The tool description adds no additional meaning about the parameter, such as formatting rules or validation. Per the baseline, since schema coverage is high, a 3 is appropriate.

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 the verb 'get' and the resource 'stock', and enumerates a specific list of outputs (totals, buy/sell split, date ranges, top members, recent trades with links, sample scored trade). This distinguishes it from sibling tools like list_transactions (raw transactions) and get_member (single member), making its purpose unmistakable.

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 makes it obvious this tool is for a single ticker's aggregated congressional trading summary, but it does not explicitly name alternatives or state when to prefer this over list_transactions or get_filing. The context is clear enough that an agent would know to use it for per-stock overviews, but there is no direct exclusion guidance.

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