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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false. The description adds the cost ($0.005) and outlines the output fields (age, liquidity, buy/sell flow, risk flags), which are useful behavioral details beyond the annotations. No contradiction exists.

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 sentence that front-loads the core purpose ('Brand-new Solana pools'), then efficiently adds cost and data composition. Every word earns its place with no redundancy.

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 covers what the tool returns (age, liquidity, buy/sell flow, risk flags) and the cost. Annotations handle the safety profile, so nothing essential is missing for an agent to decide when and how to call it.

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 covers 100% of parameters with descriptions for minLiquidity and maxAgeMinutes. The tool description does not add any extra meaning about these parameters beyond what the schema already provides, so the baseline of 3 applies.

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 resource (Solana pools) and the distinguishing attribute (brand-new, seconds to minutes old). It also lists the data included (age, liquidity, buy/sell flow, risk flags), making it distinct from siblings like get_trending_pools or get_token_snapshot.

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 phrase 'the most perishable data here' implies this is for the newest pools, but it does not explicitly name alternatives or conditions for when not to use it. The usage context is implied rather than stated, so an agent must infer that fresher data is the intended use case.

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