get_listings

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

With no annotations, the description carries the burden of behavioral disclosure. It adds cost information and the fact that results are ranked by market cap, but does not mention read-only nature, authentication needs, or rate limits. The description provides some transparency but lacks detail.

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 short sentences with no wasted words. The first sentence front-loads the purpose, and the second adds key details (cost and limit). 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?

The tool is simple with no required parameters and an output schema present. The description covers the main purpose and cost, but lacks explanation of pagination parameters (start). It is adequate but could be more complete by describing the parameters.

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 2 parameters with 0% description coverage, and the tool description does not explain what 'limit' and 'start' do. The phrase 'Returns up to 100 tokens' hints at limit but is not linked to the parameter. No value is added beyond the schema for parameter understanding.

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 explicitly states 'Get top token listings by market cap', providing a specific verb, resource, and sorting criterion. It also mentions the return limit of up to 100 tokens, which distinguishes it from siblings like get_trending or search_token.

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 usage for retrieving top tokens by market cap and mentions cost ($0.001 USDC/query), but does not explicitly state when to use this tool instead of siblings like get_trending or search_token, nor provide any exclusions or alternatives.

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