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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions the type of data returned (trade dates, assets, amounts, conflicts) but does not explicitly state that the operation is read-only, that it requires a symbol, how results are filtered, or any limitations such as date ranges or pagination. This is similar to the 'update_drive' example, which scored 2 due to missing behavioral context.

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 concise (two sentences) and front-loaded with the primary action. The second sentence adds specific data fields, but it is somewhat redundant with the first sentence ('Monitor' vs. 'Access detailed information'). Still, it is efficient and avoids unnecessary fluff.

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 parameter, no output schema), and the description covers the high-level purpose and some return fields. However, it omits critical context: the need to specify a stock symbol, how the tool behaves without valid input, and how it relates to similar Senate-trade endpoints. Given the absence of an output schema, these gaps reduce completeness.

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 'symbol' has a description 'Stock symbol'), so the baseline is 3. The tool description does not add additional meaning beyond the schema; it mentions 'assets' but does not clarify that the 'symbol' parameter filters trades by that asset. Thus, the description adds no extra value over the schema.

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 purpose: monitoring US Senator trading activity via the FMP Senate Trading Activity API. It names the resource (Senators' trades) and mentions specific data fields (trade dates, assets, amounts, conflicts of interest). However, it does not differentiate from sibling tools like getSenateTradesByName or getLatestSenateDisclosures, which is a minor gap.

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 provides no guidance on when to use this tool versus alternatives. It does not mention that the required 'symbol' parameter filters results by a specific stock, nor does it contrast with similar Senate-trade tools. There is no statement about use cases, exclusions, or prerequisites, leaving the agent to infer context from the name alone.

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