hedera_get_contract_info

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

No annotations are provided, so the description carries full burden. It only states 'Read from Mirror Node', which implies a non-destructive query, but fails to disclose rate limits, authentication needs, or data freshness. With no behavioral details beyond the verb, transparency is low.

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, clear sentence that efficiently states the tool's purpose and key returned fields. No wasted words.

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 simple read tool with one parameter and no output schema, the description is mostly adequate but missing parameter format guidance and differentiation from sibling read tools. The mention of specific return fields adds value, but the lack of parameter semantics leaves a gap.

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 single parameter contractId has no description in the schema (0% coverage). The tool description does not explain its format (e.g., '0.0.12345') or constraints. It only mentions return fields, leaving the parameter's meaning entirely to the agent's inference.

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' and the resource 'contract info from Mirror Node', listing specific fields (admin key, bytecode metadata, EVM address). It distinguishes from siblings like hedera_query_contract and hedera_get_contract_results.

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 for reading contract metadata but does not explicitly state when to use this tool versus alternatives like hedera_query_contract or hedera_get_contract_results. No exclusions or prerequisites are mentioned.

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