getSenateTradesByName

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

Annotations already declare readOnlyHint=true, idempotentHint=true and openWorldHint=true, so safety and repeatability are covered. The description adds useful scope about what is returned (trade dates, assets, amounts, conflict-of-interest flags), but says nothing about matching behavior (exact vs partial name), pagination, result limits, or how ambiguous names are resolved.

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 sentences, front-loaded with the action and filter. Minor waste in vendor branding ('with the FMP Senate Trades by Name API') and the promotional 'potential conflicts of interest' phrase, but nothing that obscures the core purpose.

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 tool is simple (one required string parameter), and with no output schema the description usefully enumerates the returned fields (dates, assets, amounts), which is the main gap it needs to fill. It falls short of 5 only because name-matching semantics and result-set behavior remain unstated.

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% and the single parameter is already documented as 'Senator name (first or last name)'. The description only restates 'by Senator name' and adds no syntax, casing, or partial-match detail beyond the schema, so the baseline of 3 applies.

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 a specific verb and resource ('Search for Senate trading activity') and the scoping filter ('by Senator name'), which implicitly separates it from the unfiltered getSenateTrades and the ID-based getSenateTradesById. It never names those siblings explicitly, so the differentiation is inferable rather than stated.

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 is only implied by the name-based filter: an agent can guess this is the right tool when it has a Senator's name but not an ID. There is no explicit when-to-use/when-not guidance, no mention of getSenateTradesById or getHouseTradesByName as alternatives, and no prerequisites or coverage caveats.

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