dero_get_block_template

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

Annotations already declare readOnlyHint=true, and the description adds the important behavioral fact that this tool returns a template payload without submitting a block. It could disclose a bit more about response structure or failure behavior, but the non-submission clarification is valuable beyond the 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?

The description is well-structured with clear sections: purpose, when to call, critical input requirements, and output. It front-loads the most important usage guidance and each sentence supports tool selection or invocation without unnecessary filler.

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 tool with no output schema and moderate parameter complexity, the description covers when to use it, the required parameters, the optional parameters, and the high-level output. It stops short of describing the exact block template fields, but it gives enough context for an agent to call the tool correctly for mining purposes.

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%, so the baseline is 3. The description repeats most parameter meanings from the schema, such as 'block' including the raw block blob and 'miner' as an optional label. It adds only minor emphasis that wallet_address must be valid and receive the reward, but does not substantially expand parameter semantics.

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 uses a specific verb and resource: 'Get a mining block template for a miner payout address via DERO.GetBlockTemplate.' It also distinguishes itself from the sibling tool dero_get_last_block_header, making the tool's unique purpose immediately clear.

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 'When to call' section explicitly restricts this tool to actual mining and names dero_get_last_block_header as the preferred alternative for general chain-tip inspection. It also clarifies that the tool does NOT submit a block, which helps the agent avoid misuse.

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