midl_convert_btc_to_evm

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

Description adds context beyond annotations: it specifies deterministic mapping via keccak256 and mentions key length options. Annotations already indicate read-only and non-destructive behavior (readOnlyHint=true, destructiveHint=false), so the description complements but does not contradict.

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 concise sentences with no fluff. Every sentence earns its place: first sentence defines purpose and input format, second explains the deterministic property and algorithm.

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 one parameter and no output schema, the description covers input format and core behavior. It lacks explicit mention of the output EVM address format (e.g., '0x-hex'), but that is standard and easily inferred. Minor gap for completeness.

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 covers 100% of parameters with a regex pattern, but the description adds meaning by clarifying the key is a Bitcoin public key and explaining the compressed/uncompressed distinction, which matches the pattern lengths (66 vs 130 hex characters).

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?

Description clearly states it derives an EVM address from a Bitcoin public key, specifying key formats (compressed 33-byte or uncompressed 65-byte hex) and the deterministic mapping via keccak256. This distinguishes it from sibling tools like bridges and transactions.

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?

Usage is implied but no explicit guidance on when to use this tool versus alternatives (e.g., when preparing for a bridge operation). No when-not-to-use or exclusion conditions are mentioned.

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