get_ltc_mempool_summary

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

Annotations already provide readOnlyHint, etc. Description adds value by stating it is READ-ONLY (redundant but clear) and that it requires LITECOIN_RPC_URL. No contradictions with annotations.

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?

Two short, front-loaded sentences with no wasted words. Every sentence adds value: READ-ONLY, data source, mirror relationship, configuration requirement.

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 no parameters, no output schema, and rich annotations, the description covers purpose, data origin, prerequisites, and cross-reference to sibling. Complete for this simple tool.

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, so schema coverage is 100%. Description does not add parameter info, but baseline for 0 params is 4. The description is sufficient.

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?

Description clearly states it returns litecoind getmempoolinfo output and is a mirror of get_btc_mempool_summary for LTC. Verb 'get' and resource 'mempool summary' are specific, and the tool is distinguished from its BTC sibling.

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?

Implicitly indicates when to use (for Litecoin mempool info) and mirrors an existing BTC tool, but lacks explicit when-not-to-use or alternative references beyond the sibling. The requirement for LITECOIN_RPC_URL is noted.

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