get_top_solana_protocols

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

No annotations provided, but description is transparent about return data and purpose. For a read-only tool, no further behavioral details are necessary.

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 with no redundancy. Each sentence adds value: first defines the tool, second gives usage guidance.

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?

No output schema, but description enumerates returned fields. Tool is simple and well-documented for its purpose.

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 covers both parameters with descriptions. The description adds context by stating the ranking basis (TVL) and output fields, which complements the schema.

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 retrieves top Solana DeFi protocols ranked by TVL, specifies the returned fields (name, TVL, category, percentage changes), and distinguishes from siblings like get_protocol_tvl by focusing on overall landscape comparison.

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 says to use when user asks about overall Solana DeFi landscape or wants to compare protocols. Does not explicitly state when not to use it, but siblings are listed for inference.

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