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

No annotations are provided, so the description bears the full burden of behavioral disclosure. It states the tool lists protocols ranked by TVL but does not describe the return format, potential pagination, or any other behavioral traits. The context added is minimal beyond the core 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, concise sentence that gets straight to the point. It contains no filler words or redundant information, making it perfectly sized and front-loaded.

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 parameterless tool with no output schema, the description provides the essential function but lacks specificity about the output format (e.g., whether it returns TVL amounts, protocol names only, or additional metadata). This is adequate but leaves room for the agent to infer return details.

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 schema coverage is 100% (vacuously). According to the rubric, a baseline of 4 applies when there are no parameters, and the description does not need to add parameter semantics. The description is not lacking in this dimension.

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 returns all Sui DeFi protocols ranked by TVL. It uses a specific resource (Sui DeFi protocols) and scope (ranked by TVL), distinguishing it from sibling tools that focus on flows, yields, volume, or other specific data.

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 gives no explicit guidance on when to use this tool versus alternatives. It implies usage for obtaining a TVL-ranked protocol list, but does not mention exclusions, prerequisites, or comparisons with sibling tools like sui_overview or sui_defi_yields.

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