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

With no annotations, the description must carry the full burden. It hints at behavior like 'A real-LP sit stays six hours' and 'No exit', suggesting time-limited opportunities, but doesn't clarify permissions, reversibility, or rate limits. The phrase 'Does not sign' indicates it's a read-only or non-transactional tool, but this is vague and buried.

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 series of short, cryptic sentences that are not front-loaded with a clear purpose. While it's concise in length, the structure is disjointed, making it hard to parse. Every sentence should earn its place, but some like 'No named FOMO handle required' add ambiguity without clear benefit.

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 zero parameters, no output schema, and no annotations, the description is the sole source of information, but it's incomplete and unclear. It doesn't explain what the tool returns, the format of its output, or its exact purpose. For a tool with no structured fields, the description should be much more explicit.

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 tool has zero parameters, so the baseline score is 4. The description doesn't need to explain parameters, and it correctly avoids doing so. No additional value is added or needed here.

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 is written in cryptic trading jargon. 'New pools on this chain: live LP, still under $400k' hints at discovering fresh liquidity pools, but there's no clear verb like 'list', 'find', or 'open' that states the action. Sibling names like talon_scan or talon_radar suggest similar functionality, making it hard to distinguish from them.

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?

There is no explicit guidance on when to use this tool versus alternatives like talon_alpha or talon_pool. Phrases like 'Fresh dust drops after 45 min' and 'Off-chain printers live on talon_wire' imply use cases but don't state conditions clearly. No when-not-to-use or alternative tools are mentioned.

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