get_chain_context

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It adequately describes the conceptual data returned (compensating for the missing output schema), but omits operational details like rate limits, data freshness, error behaviors for unsupported chains, or whether results are cached vs real-time.

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?

Every sentence earns its place: the first clause defines the action and resource, the colon-delimited list specifies return values, and the final fragment enumerates valid inputs. Zero waste, appropriately 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?

Given the simple single-parameter input and lack of output schema, the description compensates well by detailing the expected return content (TVL, dominance, etc.) and listing all valid chain values. It is complete for a read-only data retrieval tool, though error scenarios could be mentioned.

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?

With 100% schema coverage, the schema already documents the parameter well. However, the description adds significant value by providing the complete enumeration of supported chains ('ethereum, solana, base...'), effectively serving as an enum constraint that the schema lacks.

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 uses a specific verb ('Get') and clear resource ('DeFi context for a specific blockchain'), then enumerates exactly what metrics are returned (TVL, dominance, trend, top protocols, market share direction). This clearly distinguishes it from sibling tools like get_asset_context (asset-level) and get_defi_health (health-focused).

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?

While the description implies usage through specificity of returned metrics, it lacks explicit guidance on when to prefer this over siblings like get_onchain_pulse or get_defi_health. No alternatives or exclusion criteria are mentioned, leaving selection logic implicit.

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