get_btc_block_tip

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

Beyond readOnlyHint annotation, describes indexer dependency (mempool.space default, configurable via env var or user-config), conditional availability of BIP-113 and difficulty fields, and normal block gap behavior. Adds significant operational context.

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 adds value. Front-loaded with core purpose and read-only flag. Followed by return fields, configuration detail, then use cases. No fluff, well-organized.

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?

Covers all relevant aspects: what the tool does, what it returns, how it's configured, and appropriate use cases. With no output schema, the description fully explains return values. 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, so schema coverage is 100%. Description adds meaning by listing return fields and their types (e.g., 64-hex hash, unix seconds) which compensates for lack of output schema. Baseline 4 for 0 parameters.

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?

Explicitly states it is READ-ONLY and returns the current Bitcoin mainnet chain tip. Lists specific return fields (height, hash, timestamp, ageSeconds, BIP-113 median time past, difficulty). Clear verb+resource, distinct from sibling tools by focusing on the single latest block.

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?

Provides explicit use cases: latest-hash lookups, block-age UX context, indexer-freshness checks, confirmation-depth math. Also explains Poisson block intervals. Does not explicitly exclude alternatives, but the guidance is clear and practical.

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