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

No annotations are provided, so the description carries the full burden. It adds the important behavioral constraint of requiring an EnsoTrade Pro API key, and implies a real-time snapshot. However, it does not disclose other behavioral aspects like whether results are sorted, paginated, or cached, though these are partly covered by the output schema.

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 two sentences with no filler. The core purpose is front-loaded, followed by usage guidance and a key requirement. Every sentence earns its place.

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 there is an output schema, return values need no explanation. The description covers purpose, usage context, and an important prerequisite (API key). The only minor gap is the undocumented 'limit' parameter, but it is a simple optional field with a default, so overall completeness is high.

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 has 0% description coverage and the description does not mention the 'limit' parameter at all. While the name and default (20) are somewhat self-explanatory, the description adds no semantic value beyond the schema, failing to compensate for the low schema coverage.

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 states a specific verb ('ranking') and resource ('whole crypto perp universe'), with clear differentiation between leading and lagging coins. It also signals its primary role as the first-step tool, distinguishing it from the sibling tools that drill deeper.

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?

Explicitly directs the agent to use this tool FIRST when asked to 'find a coin' or 'what should I look at', and contrasts it with 'the other tools' for deeper investigation. This gives clear when-to-use guidance and implicitly names alternatives.

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