hedera_get_contract_state

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

No annotations are provided, so the description must fully disclose behavioral traits. However, it only states 'Read' without confirming read-only nature, auth requirements, rate limits, pagination behavior, or what happens on error. This is a significant gap for a tool that accesses contract state.

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 sentence with no extraneous words. However, it lacks sufficient detail to be considered well-structured; it is too minimal for the task complexity.

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 the absence of annotations and output schema, the description should provide a thorough overview. It fails to explain what 'storage slots' are, how results are structured, or any constraints. The tool has 2 parameters and no output schema, so the description is incomplete.

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 0%. The description does not explain the meaning or usage of the two parameters (contractId and limit). The contractId parameter is implied by the tool's name, but limit's role in controlling result size or pagination is entirely unascribed.

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 verb 'Read', the resource 'a contract's current storage slots', and the source 'from the Mirror Node'. This distinguishes it from sibling tools like hedera_get_contract_info (which reads contract info) and hedera_query_contract (which can execute arbitrary queries).

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 provides no guidance on when to use this tool versus alternatives. There is no mention of prerequisites, limitations, or explicit context for selection among the many sibling tools.

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