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

With no annotations provided, the description carries the full burden. It only mentions the output (protocols ranked by TVL) but does not disclose whether this is a read-only operation, whether the list is exhaustive, how rankings are ordered, or what data fields are returned. Minimal behavioral context is provided.

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, front-loaded sentence with no unnecessary words. It efficiently conveys the core function without redundancy.

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?

For a simple 0-parameter tool with no output schema, the description is largely sufficient to understand what the tool returns. It lacks minor details (e.g., whether TVL is in USD, ordering direction) but is complete enough for a basic reference list. The sibling context further clarifies its niche.

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, so the description adds no parameter-specific semantics. The baseline for 0 parameters is 4, and the description does not contradict or confuse parameter usage. No additional param information is needed.

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 lists all Solana DeFi protocols ranked by TVL, using a specific verb ('list' implied) and resource ('Solana DeFi protocols') with a clear scope ('ranked by TVL'). This distinguishes it from sibling tools like sol_defi_yields (yields) and sol_dex_volume (trading volume).

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?

No explicit guidance is provided on when to use this tool versus alternatives. It does not mention any sibling tools or situations where this tool is preferable, leaving the agent to infer from the description alone.

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