get_ltc_block_tip

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

Annotations already indicate read-only and idempotent behavior. The description adds detail on returned fields, configurable indexer (with env var/user override), and a useful statistical note about block time distributions, exceeding annotation coverage.

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 slightly verbose with an issue reference and version number, but information is front-loaded and each sentence adds value. Could be trimmed slightly without losing clarity.

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?

Without an output schema, the description lists key return fields and explains configuration and behavioral context (block time tolerance), covering all necessary information for an agent to use the tool effectively.

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%. Baseline 4 applies as description does not need to add parameter meaning, but it correctly notes no input required.

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 explicitly states the tool returns the current Litecoin mainnet chain tip with specific fields (height, hash, timestamp, etc.) and clearly differentiates it from the BTC version by mirroring get_btc_block_tip.

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 mentions it mirrors the BTC tip tool and includes a note about block time expectations (2.5-min target, 10-min gap normal), but does not explicitly compare to sibling tools like get_ltc_blocks_recent or get_ltc_chain_tips.

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