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

Annotations already mark it read-only, idempotent, and non-destructive, and the description adds meaningful behavioral context: unknown ids produce a not-found error, missing authentication returns setup steps, and results are cached for up to an hour. This goes beyond what the annotations convey.

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 dense but well structured: return contents first, then usage context, then access/caching behavior. The first sentence is long and comma-heavy, which slightly reduces scannability, but every part earns its place and there is 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?

With no output schema, the description carries the burden of explaining the return value, and it thoroughly covers filer identity, roll-up numbers, trades, document link, and the sample trade. It also covers error, auth, and caching behavior, leaving an agent with everything needed to invoke and interpret the call.

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 single parameter `filing_id` is already fully documented in the schema, including its constraints, format, and where it comes from. The description reinforces that origin context but does not add new parameter-level meaning, so a baseline of 3 is appropriate at 100% schema coverage.

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 exactly what the tool returns: a single STOCK Act Periodic Transaction Report with filer details, roll-up statistics, all disclosed trades, the original document link, and the sample scored trade. The title and description clearly distinguish it from broader listing/summary sibling tools.

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 says to use it after whats_new, list_recent_filings, or get_member has provided a filing id, and that the question must be about what that one report contained. This gives clear when-to-use guidance and routes the agent away from list-level alternatives.

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