get_trader_profile

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

With no annotations provided, the description carries full burden. It indicates the tool retrieves data (assumed read-only) but does not disclose behavioral traits such as data freshness, pagination limits beyond the eventLimit parameter, or any side effects. This is minimal context for a data retrieval tool.

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 purpose and enumerates key data points without extraneous words. Every element is valuable.

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 description lists three categories of data (first appearance, CTF events, USDC flows) but does not specify the structure or types of events. Given no output schema and no annotations, more detail on the returned profile shape would improve completeness. It is adequate but not thorough.

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 covers both parameters (address, eventLimit) fully (100% coverage). The description adds no additional meaning beyond what the schema provides. At baseline, the schema does the work, so a score of 3 is appropriate.

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 specifies the verb 'Get' and the resource 'trader's on-chain profile', listing concrete data points (first appearance, CTF events, USDC flows). It distinguishes itself from sibling tools by focusing specifically on trader profile data.

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 the tool is for fetching trader profile information but does not provide explicit guidance on when to use it versus sibling tools (e.g., get_top_traders, get_trader_usdc_flows). No exclusions or contexts are described.

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