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

With no annotations, the description carries the transparency burden. It discloses that the registry includes 'known gotchas' and direct links to endpoints, which adds context, but it does not explicitly state read-only behavior, safety implications, or return format. As a getter, risk is implied low, but the description could be more explicit about side effects (none) and data completeness.

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 concise yet information-dense, using two sentences to convey scope, contents, and priority. It is front-loaded with 'Canonical machine-readable registry' and every clause adds specific value—no filler or repetition.

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?

Despite having no output schema, the description thoroughly explains the return value: a registry with addresses, proxy/impl, ABIs, gotchas, and links. It also covers usage context ('Pull this FIRST') and the breadth of contracts. For a zero-parameter tool, this is complete and self-sufficient.

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 need not explain parameter semantics. The baseline for zero parameters is 4, and the description adds value by detailing what the registry contains, which is more relevant than parameter docs here.

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 identifies the tool as a canonical registry of all MEGA Protocol contracts, enumerating specific categories (tokens, AMM pair, staking, governance, emissions, safety) and key contents (addresses, ABIs, gotchas). It uses a specific verb+resource and distinguishes itself from sibling get_* tools by its exhaustive scope and 'registry' framing.

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 explicitly instructs 'Pull this FIRST for any DeFi interaction,' providing a clear when-to-use directive and positioning it as a prerequisite. It does not explicitly name alternatives or when-not-to-use scenarios, but the context is unambiguous given its registry role.

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