latest_token_profiles

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

With no annotations provided, the description must carry the transparency burden. It conveys that the tool returns recent token profiles but omits behavioral details such as ordering, pagination, time windows, or potential duplicates. The description is not misleading but provides minimal insight beyond the basic purpose.

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 verb 'Get' and immediately states the resource. It contains no filler or redundant information, making it highly concise and scannable.

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 tool's simplicity (no parameters, no output schema), the description adequately conveys what it does. It could be more explicit about the return format or that it returns a collection of profiles, but for a basic fetch tool the context is sufficient.

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, and the input schema is empty with 100% coverage by definition. Per the rubric, 0 params earns a baseline of 4, and the description does not need to explain parameter semantics.

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 tool fetches 'latest token profiles freshly listed/updated on DexScreener' with the intent of finding 'new tokens to watch.' This specific verb+resource combination distinguishes it from sibling tools like 'top_boosted_tokens' or 'search_pairs'.

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 provides a clear use case ('new tokens to watch') and implies it is for fresh listings/updates. However, it does not explicitly mention when not to use it or name alternative tools for different scenarios, such as searching for specific pairs or getting top boosted tokens.

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