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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states the core function, which is a read operation, but does not disclose any additional traits such as rate limits, error behavior, or output format. It is not misleading, but it provides minimal behavioral context beyond the obvious purpose.

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 concise sentence with no wasted words. It is front-loaded with the purpose and contains no extraneous information. This is ideal for a simple tool and earns full marks for conciseness.

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?

Given the simplicity of the tool (two parameters, no output schema), the description is minimal but not entirely inadequate. It tells the agent what the tool does but does not explain the return format or the effect of the 'limit' parameter. For a tool with no output schema, more detail on the expected result would be helpful, so a 3 reflects this gap.

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 schema description coverage is 0%, so the description must compensate. It explains that the primary parameter 'mint' refers to a token mint, which adds meaning, but it says nothing about 'limit'. Since only one of two parameters gets any contextual explanation, the description only partially compensates for the lack of schema descriptions, warranting a low score.

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 verb ('Recent on-chain trades') and the resource ('token mint'), so an agent knows what the tool does. However, it does not differentiate it from sibling tools like top_traders or whale_ticker, which also deal with trade data. The purpose is clear but lacks sibling distinction, so a 4 is appropriate.

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 guidance on when to use this tool versus alternatives. It does not mention scenarios, exclusions, or refer to any sibling tools. An agent has to infer that this is for recent trades on a specific mint, but there is no explicit context on when it is preferred over other trade-related tools.

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