get_network_snapshot

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

With no annotations provided, the description carries the burden of behavioral disclosure. It transparently states that the tool is free and requires no wallet (authentication), which is valuable context. However, it does not explicitly mention that the operation is read-only, side-effect-free, or discuss rate limits or error conditions. The field list gives a sense of the response, but additional behavioral guarantees are absent.

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 a single, succinct sentence that leads with the tool's purpose, enumerates the key data points, and adds a cost/access note. There is no fluff or redundancy; every phrase contributes value.

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 simplicity of the tool (no parameters, no output schema), the description provides a sufficient list of the returned data elements. It could elaborate on the format of the mempool summary or the timestamp, but the core information is covered, making it complete enough for an agent to understand the tool's output.

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, and the schema is empty (100% coverage). The description does not need to explain parameters, and the absence of parameters is clear from the schema. This satisfies the baseline for no-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 clearly states the tool provides a Bitcoin network snapshot and enumerates specific data fields (chain height, best block hash, peers, sync state, mempool summary). This distinguishes it from sibling tools like get_mempool_snapshot, which focuses only on the mempool, and get_status, which may not include the same field set.

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 implies usage for obtaining a broad network overview, and the phrase "FREE — no wallet needed" suggests it is suitable for public, unauthenticated access. However, it does not explicitly state when to prefer this tool over alternatives like get_mempool_snapshot or get_status, leaving the decision to the agent.

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