runtime_metricsRead process-local resolver/rung/RPC counters for smoke checks and reliability dashboards.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
| Name | Required | Description | Default |
|---|---|---|---|
| metrics | Yes | ||
| uptime_seconds | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and openWorldHint=true. The description adds that the tool reads process-local counters, confirming it is safe and local. No contradictions, and the description usefully supplements annotations with behavioral context about what specific data is read.
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?
A single, well-structured sentence that is front-loaded with the verb and resource. Every word serves a purpose, and there is no superfluous content.
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 simple tool with no parameters and an output schema, the description sufficiently explains what the tool does and its intended use. It could be slightly more explicit about the return format, but the output schema likely covers that, so completeness is adequate.
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?
There are no parameters (schema coverage 100% trivially). The description adds meaning by specifying that the tool reads 'resolver/rung/RPC counters', which provides context beyond the empty schema. This is above the baseline of 4 for zero-parameter tools.
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 specifies the verb 'Read' and the exact resource 'process-local resolver/rung/RPC counters', along with the purpose 'for smoke checks and reliability dashboards'. It clearly distinguishes from sibling tools which are about transactions, encoding, and contract interactions.
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 provides clear context that the tool is intended for smoke checks and reliability dashboards, implying use for monitoring or health checks. However, it does not explicitly state when not to use or mention alternatives, but given the distinct purpose and sibling tools, the usage guidance is adequate.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool has a clearly distinct purpose: decode vs encode, prepare vs simulate, resolve ABI vs selector, etc. No two tools overlap in functionality.
All tool names follow a consistent verb_noun pattern with lowercase and underscores (e.g., decode_tx, list_chains, resolve_abi, runtime_metrics). The only exception is 'simulate', which is a single verb but still clear and consistent with the style.
12 tools is an ideal count for a blockchain interaction server. Each tool covers a necessary step in the workflow without being overwhelming or sparse.
The tool set covers the full lifecycle of contract interaction: resolve ABI, encode/decode, simulate, prepare unsigned transactions, look up selectors, resolve names, and list chains. No obvious gaps given the server's purpose of preparing actions for external signing.