dero_get_block_template

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

Annotations (readOnlyHint=true, destructiveHint=false) are present, and the description adds behavioral context beyond annotations, such as noting that the tool does NOT submit a block and mentioning the excluded DERO.SubmitBlock method. 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 organized into three clear paragraphs: purpose, usage guidance, and input/output details. It is concise and front-loaded with key information, though could be slightly tighter 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?

Given 3 parameters, no output schema, and annotations present, the description provides sufficient context: input requirements, output purpose (block template for mining client), and what the tool does not do. It is complete for an agent to select and invoke correctly.

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?

Schema description coverage is 100%, but the description adds value by emphasizing wallet_address format (dero1... or deto1...), explaining the optional block parameter's effect, and noting miner as an optional label. This provides semantic 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 the tool's purpose: 'Get a mining block template for a miner payout address'. It provides a specific verb (get) and resource (mining block template), and distinguishes from sibling tool dero_get_last_block_header by specifying when to prefer each.

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?

Explicit usage guidance is given: 'When to call: ONLY when you are actually mining. PREFER dero_get_last_block_header for general chain-tip inspection.' This clearly indicates when to use this tool and when to use an alternative.

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