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. While 'Get' implies a read-only operation, it does not mention whether data is real-time, if pagination exists, or how 'win rate' is calculated. No side effects, data freshness, or limitations are disclosed.

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 a single, front-loaded sentence that conveys the core action and criteria efficiently. The parenthetical adds a useful analogy without excessive verbosity, though it is not strictly necessary.

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 zero-parameter tool with no output schema, the description states what is returned but omits important details such as the exact fields in the result, ordering, or any caveats about data availability. An agent could call the tool correctly, but might not fully know what format to expect.

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?

The input schema is empty (0 parameters), so schema description coverage is 100%. The description adds context about the result selection criteria but does not need to explain parameters; the baseline of 4 for zero-parameter tools 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?

The description clearly states a specific verb ('Get'), a resource ('European corporate insiders'), and precise criteria ('10 ... highest 12-month win rates and average returns'), making it easy to distinguish from sibling tools like get_cluster_buys or get_recent_filings. The parenthetical 'Pelosi-equivalent tracker' adds useful context without ambiguity.

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 gives no explicit guidance on when to use this tool over the sibling tools. It does not mention alternatives, exclusions, or conditions under which this tool is preferred, leaving the agent to infer its use case solely from the stated output.

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