get_difficulty_adjustment

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

With no annotations provided, the description carries the full disclosure burden. It successfully specifies what the tool computes (the four listed metrics), but omits operational context such as whether this requires live network access, data freshness guarantees, or computational cost relative to other queries.

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 single, information-dense sentence structured as 'action: specific outputs'. Every word serves a purpose, with the colon-delimited list efficiently conveying the return value structure without verbose explanation.

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 zero parameters and the presence of an output schema (which handles return value documentation), the description is appropriately complete. It adds value by listing the conceptual metrics calculated, which helps the agent understand the tool's specific utility within the mining analysis domain.

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 input schema contains zero parameters, which per guidelines establishes a baseline score of 4. The description appropriately makes no mention of parameters since none exist, requiring no additional semantic clarification.

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 ('Calculate') with a clear resource ('difficulty adjustment progress') and enumerates exactly what metrics are returned (blocks into epoch, blocks remaining, estimated time, projected adjustment). It clearly distinguishes from siblings like get_mining_info (general stats) or get_halving_countdown (different epoch type).

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 implies usage context through the specific metrics listed (use when tracking difficulty epoch progress), but provides no explicit guidance on when to prefer this over alternatives like get_mining_info or get_blockchain_info, nor does it mention prerequisites such as node synchronization requirements.

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