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

Annotations already declare readOnlyHint and destructiveHint false, so the safety profile is covered. The description adds meaningful behavioral context beyond annotations: results are newest first, date range defaults to one year, amounts are disclosed ranges rather than exact values, and Asset identifies the filed instrument type (stock, option, bond). This enriches the agent's understanding without contradicting annotations.

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 with no fluff: the first sentence states the core function and defaults, the second clarifies data semantics, and the third directs to the sibling tool. All information is front-loaded and each sentence earns its place.

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 appropriately explains what the response contains: members, purchase/sale, transaction/filing dates, amount ranges, and instrument type. It also covers defaults and ordering. Given the tool's moderate complexity, the description is sufficiently complete for an agent to know what to expect and how to invoke it.

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 baseline is 3. The description adds value by clarifying semantic nuances not fully explicit in the schema: that amounts are ranges not exact values, that Asset identifies instrument type, and that transactions are reported by members of Congress. This supplements the parameter descriptions meaningfully.

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 tool retrieves congressional securities transactions for a specific ticker, with a scope qualifier ('newest first, last year by default'). It distinguishes itself from siblings by explicitly pointing to GetMemberTrades as the alternative for one member's transactions across tickers.

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?

Usage context is explicit: use for a specific ticker, and 'Use GetMemberTrades for one member's transactions across all tickers' directly names the alternative. This provides clear when-to-use guidance and prevents confusion with sibling tools.

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