Unlock blockchain analysis (start here)

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

Describes the tool as returning usage rules and conventions, implying safe, read-only behavior. Lacks mention of idempotency or effects of repeated calls, but given no annotations, the disclosure is adequate for its simplicity.

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 essential information front-loaded: 'MANDATORY FIRST STEP.' No unnecessary words—every sentence carries key 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?

Given the tool has an output schema (implied to detail the rules), the description fully covers the tool's purpose and usage. It tells the agent exactly what to do and why, leaving no gaps.

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?

No parameters exist, and schema coverage is 100%, so no additional parameter documentation is needed. The baseline of 4 is appropriate as the description adds no extra meaning beyond the empty 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 is the mandatory first step that returns usage rules and conventions, distinguishing it from all sibling tools that perform blockchain analysis tasks.

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 'MANDATORY FIRST STEP' and 'Call this once before invoking any other tool,' providing unambiguous when-to-use and ordering instructions.

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