get_top_traded_assets

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

With no annotations, the description must carry the behavioral burden. It states the ranking criterion ('ranked by number of trades') and the scope ('by politicians'), but it does not disclose return format, whether buys and sells are combined, or any other caveats. As a read-only 'Get' tool, the safety profile is inferable, but additional details would improve transparency.

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, well-structured sentence that front-loads the core purpose and includes all key details (asset types, actor, time period, ranking) without redundancy or wasted words.

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 list tool with two optional parameters and no output schema, the description is largely complete. It tells the agent what the tool returns (top traded assets) and how they are ranked. However, lacking any mention of the response structure is a minor gap, given the absence of an output schema.

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% for both parameters (days and limit), so the baseline is 3. The description adds a semantic link by mentioning 'over a time period' (mapping to days) but does not explain limit or provide value beyond the schema's existing descriptions.

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 identifies the verb ('Get'), the resource ('most traded assets'), and the specific qualifiers ('by politicians over a time period, ranked by number of trades'). It effectively distinguishes itself from siblings like get_asset_stats (per-asset stats) and get_buy_momentum_assets (momentum-based) by focusing on aggregated trade frequency.

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 a use case (ranking assets by politician trading activity) but does not explicitly state when to use this tool versus alternatives like get_politician_trades or get_party_buy_momentum. There is no mention of exclusions or specific scenarios, so guidance is implied rather than explicit.

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