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

The annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description usefully adds that no network call is made and that output is 0x-prefixed, but it sits in mild tension with openWorldHint=true, which implies external-world interaction; the description does not acknowledge that nuance.

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?

Two tight sentences: the conversion is front-loaded and the 'pure conversion' caveat follows immediately. Every clause carries information; nothing is redundant or buried.

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 one-parameter, no-output-schema utility, the description covers input format, output format and side-effect profile, which is essentially everything an agent needs. It only falls short of a 5 because the openWorldHint tension is left unexplained.

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% and the single parameter is fully documented there, so the baseline is 3. The description restates the input form ('0.0.x' realm-shard-num) and adds the output shape (0x-prefixed EVM address), but contributes no syntax or edge-case detail beyond the schema.

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?

States a precise verb+resource ('Convert a Hedera contract ID ... to its 0x-prefixed EVM address') and specifies the exact input form ('0.0.x' realm-shard-num). It is clearly distinguishable from the sibling hederaAccountIdToEvmAddress because it operates on contract IDs, not account IDs.

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 clause 'Pure conversion - does not query the network' implies when this is appropriate (offline/deterministic use, no RPC needed), but it never explicitly routes the agent between this tool and the sibling hederaAccountIdToEvmAddress or states prerequisites. Usage is inferred rather than stated.

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