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

While annotations already declare readOnlyHint=true and destructiveHint=false, the description enriches understanding by detailing default behaviors for 'code' and 'variables' (both default true), how to skip them for efficiency, and the meaning of omitting or using -1 for 'topoheight'. It also discloses the output shape, which is absent from annotations or schema. No contradictions exist; the description complements the annotations perfectly.

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 longer than typical but exceptionally well-organized with clear headings: 'Input Requirements (CRITICAL)' and 'Output'. Every sentence adds value: usage context, defaults, and output shape. While it could be considered verbose for a simple getter, the complexity of the tool justifies the length. No fluff; each line is functional.

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 there is no output schema, the description compensates by defining the return structure ('{ code, balances, variables: { stringkeys, uint64keys }, ... }'). It also covers default behaviors, parameter edge cases (omitting topoheight), and practical usage tips. For a tool with 4 parameters and no output schema, this description leaves no critical information gaps.

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 parameter purposes but adds minimal new semantic detail beyond schema descriptions; it does clarify the default values and the '-1 for latest' convention for topoheight, which is also in the schema. The output format note is helpful but not parameter-specific. Thus, it meets but does not exceed the baseline.

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 opens with a specific verb+resource: 'Read smart contract state (code and/or stored variables) by SCID'. It immediately distinguishes itself as 'the primary entry point for any contract inspection on DERO,' clearly differentiating it from sibling tools like 'dero_get_transaction' or 'explain_smart_contract'. No ambiguity about what the tool does.

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?

Explicitly states when to call: 'as the first step in any DVM contract investigation.' It also gives guidance on complementing with dero_docs_search for interpretation, and even instructs to prefer citing docs pages. This goes beyond basic usage and provides a clear decision path, covering both when and how to use the tool effectively.

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