get_ltc_blocks_recent

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

Annotations already declare readOnlyHint true, destructiveHint false, idempotentHint true, openWorldHint true. The description adds specifics: READ-ONLY, default 144 blocks (~6h), capped at 200, and internal usage context. No contradictions.

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 tight three-sentence paragraph, front-loaded with 'READ-ONLY', and every sentence adds value (function, defaults, internal usage). No wasted words.

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 list tool with no output schema, the description adequately specifies it returns block headers newest-first, with defaults and cap. It mentions internal usage and issue reference. Minor omission: could briefly note typical fields in a block header, but not required.

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 schema provides 100% coverage for the single limit parameter. The description adds reasoning for the cap (to bound HTTP fan-out on litecoinspace.org's tighter free tier), providing meaningful context beyond the schema.

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 it fetches recent Litecoin block headers, newest-first, with default limit and cap. It explicitly mirrors get_btc_blocks_recent for LTC, distinguishing it from sibling tools like get_ltc_block_tip or get_ltc_block_stats.

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 notes it is used internally by get_market_incident_status for LTC and mentions the cap bound due to API tier. However, it does not explicitly state when to use this tool versus alternatives like get_ltc_block_tip or get_ltc_block_stats.

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