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

With no annotations provided, the description carries the burden for behavioral disclosure. It mentions the type of information returned (trade dates, assets, amounts, conflicts of interest), but does not disclose operational details like data coverage, pagination, or matching behavior (e.g., exact vs partial name). It is a read-search operation, but this is implied rather than explicit.

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 two sentences long, front-loads the core purpose, and includes only relevant details about the return content. Every phrase earns its place, and there is no wasted text.

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 one-parameter tool without an output schema, the description covers the essential purpose and what information is returned. It could mention edge cases like multiple senators with the same name or how name matching works, but these are not critical for a basic search tool.

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%, as the 'name' parameter already has a description. The tool description adds minimal semantic value beyond restating 'by Senator name' and 'specific Senators', so it does not exceed the baseline of 3.

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 searches for Senate trading activity by Senator name, using a specific API. The verb 'Search' and resource 'Senate trading activity' are specific, and the focus on Senator name distinguishes it from siblings like getSenateTrades (which lists all trades) and getHouseTradesByName (House vs 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 you need trades for a specific Senator, mentioning 'specific Senators' and 'by Senator name'. However, it does not explicitly name alternatives or state exclusions, so it falls slightly short of a 5.

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