getSenateTrades

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so the safety profile is covered. The description adds value by enumerating what the response contains (trade dates, assets, amounts, potential conflicts of interest), but says nothing about coverage limits, date ranges, pagination, or whether results are historical-only.

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 resource, with no redundancy. The only slack is the vendor plug 'with the FMP Senate Trading Activity API', which conveys nothing an agent needs for selection.

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 one-parameter, no-output-schema tool the description is close to sufficient on what data comes back, but it omits the two things that matter most for correct invocation: that a ticker is mandatory and how this differs from the many sibling Senate/House disclosure tools. Adequate but noticeably incomplete relative to the crowded sibling set.

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% and there is a single required parameter documented as 'Stock symbol', so the baseline is 3. The description does not compensate at all — it never mentions that a symbol is required or that results are filtered to that ticker, which is the one piece of meaning it could usefully have added.

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 names the resource (US Senate trading activity) with verbs like 'Monitor' and 'Access', and even lists returned fields such as trade dates, assets, amounts and conflicts of interest. However, it never states the crucial distinguishing trait that this endpoint is symbol-scoped, so an agent cannot tell it apart from siblings like getSenateTradesByName, getSenateTradesById, or getLatestSenateDisclosures from the text alone.

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?

There is no when-to-use guidance and no exclusions — nothing says to prefer this over the by-name or by-id variants, or over the general Senate disclosures feed. The word 'Monitor' hints at ongoing tracking but gives the agent no decision rule.

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