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

Annotations already convey readOnlyHint, openWorldHint, and non-destructiveness. The description adds meaningful context by clarifying that this surfaces scheduled buying/selling pressure and by naming the returned metrics (deposit size, amount spent, amount accumulated, status). It does not contradict annotations.

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?

Two tight sentences with no filler. The core purpose is front-loaded, followed by usage guidance and a chain restriction. Every sentence earns its place.

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 an output schema exists and annotations cover safety, the description is largely sufficient: it provides purpose, a concrete use case, a sibling distinction, and a chain constraint. It omits filter behavior, but the schema documents the filtering parameters, so the practical gap is small.

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 description coverage is reported as 0%, and the description does not compensate for the input parameters. It says nothing about tokenAddress, status, traderAddress, depositUsdValue, includeSmartMoneyLabels, or page; only output concepts are mentioned, so it adds little beyond 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 opens with a specific verb and resource: 'Get Jupiter DCA (dollar-cost-averaging) orders opened against a Solana token', and lists key returned fields. It also clearly distinguishes itself from token_dex_trades, so an agent can differentiate sibling tools without opening schemas.

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 explicitly states when to use this tool ('see scheduled buying or selling pressure that has not hit the market yet') and names the alternative for executed trades ('use token_dex_trades for trades already executed'). It also restricts scope to Solana tokens, leaving no ambiguity.

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