getSenateTradesByName

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

Annotations already indicate readOnlyHint=true and idempotentHint=true. The description adds that the tool returns 'detailed information on trades ... including trade dates, assets, amounts, and potential conflicts of interest'. However, it does not disclose pagination, limits, or response structure beyond this.

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 concise sentences with no extraneous information. The first sentence states the core function, and the second specifies what information is accessible. Front-loaded and efficient.

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 simple tool with one parameter and good annotations, the description covers the purpose and output content. However, it lacks information on error handling, multiple returns, or how to interpret the 'conflicts of interest' part. Still, it is largely complete for the tool's simplicity.

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 coverage is 100% (the only parameter 'name' has a description). The description's mention of 'first or last name' adds minor clarification, but the schema's description already says 'Senator name (first or last name)', so no significant added value.

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's verb ('Search for') and resource ('Senate trading activity by Senator name'). It differentiates from siblings like 'getSenateTrades' by specifying the name filter and from 'getHouseTradesByName' by specifying Senate.

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 usage when searching by name, but does not explicitly state when to use this tool over alternatives like 'getSenateTrades' (which may list all trades). No when-not-to-use or alternative guidance is provided.

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