madeonsol_token_get

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

Annotations already indicate read-only, idempotent, open-world, and not destructive. The description adds behavioral context by listing the specific data returned (e.g., VWAP, deployer reputation, KOL activity) and mentions an 'ULTRA' feature for KOL wallet addresses, enhancing transparency beyond 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 efficiently convey the tool's purpose and key data fields, with critical details front-loaded. No superfluous words; every sentence adds value.

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 the simple input (single mint address) and lack of output schema, the description adequately covers expected return fields and the optional ULTRA addition. Missing details on error responses or pagination, but these are unlikely given the tool's nature.

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 coverage is 100%, with parameter 'mint' described as 'Token mint address (base58)'. The description reinforces that the tool operates per-mint but adds no new semantic information beyond what the schema provides.

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 'Comprehensive per-mint snapshot' and enumerates specific data fields (price, market cap, volume, etc.), distinguishing it from sibling tools that focus on specific aspects (e.g., madeonsol_token_candles for candlestick data, madeonsol_token_risk for risk).

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 implies use for a broad overview of a token's metrics but does not explicitly specify when to use this tool instead of specialized siblings like madeonsol_token_flow or madeonsol_token_buyer_quality. No 'when not to use' or alternatives are mentioned.

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