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

No annotations are provided, so the description must fully disclose behavior. It states the return content (protocol categories, addresses, features, links) but omits any details about read-only behavior, data freshness, pagination, or potential side effects. The verb 'Returns' implies a read operation, but without annotations, the transparency is minimal.

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, leading with the action verb 'Returns' and providing concise, relevant details (protocol types, included data). Every sentence earns its place with no filler or 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?

The tool has no params, no output schema, and no annotations, so the description carries the context burden. It adequately describes the content (protocol types and included fields) for a simple directory lookup, but lacks usage guidance or clarification on how it relates to get_protocol_registry. Given the low complexity, this is nearly complete, but the missing sibling differentiation prevents a 5.

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 input schema is empty with zero parameters, so there are no parameters to describe. According to the rubric, 0 params warrants a baseline score of 4. The description doesn't need to add parameter details, and it doesn't contradict 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 states a specific action ('Returns') and resource ('curated directory of protocols on MegaETH'), with concrete examples (DEXes, bridges, payment infra, storage, identity systems) and content details (contract addresses, features, links). This clearly distinguishes it from siblings like get_bridge_info (specific bridge details) and get_protocol_safety (safety ratings).

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 a general directory lookup, but there is no mention of when to prefer it over similar siblings like get_protocol_registry or get_bridge_info. No exclusions or alternative contexts are provided.

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