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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds useful scope and output context (Solana, deposit size, amount spent, order status), but it does not disclose pagination, default ordering, or other query behavior. No contradiction with 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 sentences, front-loaded with the core purpose and followed by a single routing note. No filler, no repetition, 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?

For a read-only tool with an output schema, the description covers the core purpose, Solana scope, returned data categories, and the key sibling distinction. It omits pagination and default sort behavior, but the schema's property descriptions and output schema fill in much of the remaining detail.

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 at 0%, so the description needed to compensate by explaining how to use the sole `request` parameter. It does not: it only describes what the tool returns, not how to construct the request object. The nested schema fields are documented, but the description itself adds no parameter-level meaning.

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 by smart traders and funds on Solana.' It also names the included fields (deposit size, amount spent, order status) and explicitly distinguishes it from the one-off-swap sibling tool, so an agent can tell it apart from the many smart_traders tools.

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?

It states the intended scenario directly: 'Use this for scheduled accumulation intent.' It also names the alternative for the opposite case: 'use smart_traders_and_funds_dex_trades for one-off swaps.' This is an explicit when-to-use and when-not-to-use signal.

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