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

With no annotations, the description bears the full responsibility for behavioral disclosure. It states that the output includes AI-generated direction, confidence, and win rate, which is useful context, but it does not mention side effects, latency, authentication, or the behavior when no token filter is provided. The read-only nature is only implied by the name.

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 phrase that is front-loaded with the tool's purpose. It contains no wasted words and directly communicates the core value proposition.

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?

With only one optional parameter and no output schema, the description should clarify the default return behavior and response shape. It names the output fields but does not explain what happens when the token filter is omitted or whether the result is a list or single object. This makes it minimally adequate but with clear gaps.

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 input schema already describes the 'token' parameter as a filter by mint address with 100% coverage. The description adds no extra meaning beyond what the schema provides, so the baseline score of 3 is appropriate.

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 identifies the resource (trading signals) and specifies the key attributes (direction, confidence score, win rate) for Solana tokens. The verb is implied by the tool name 'get', and the content distinguishes it from siblings like competitor intel or market regime.

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?

No explicit guidance is provided on when to use this tool versus alternatives. The description is purely definitional and does not mention any exclusions, prerequisites, or when one might prefer a sibling tool.

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