get_address_from_pubkey

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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds the useful behavioral fact that the tool works offline and that pubkeys may be compressed or uncompressed, but it does not disclose error behavior or output format, which is partly covered by the output schema.

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 core purpose is front-loaded in one sentence, and the Args block is compact and directly aligned with schema properties. Every line adds relevant information with no filler.

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-only conversion tool with an output schema, the description covers the essential inputs and offline behavior. It does not fully explain what 'all' produces or which network values are valid, but the output schema and parameter defaults mitigate the 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?

Schema description coverage is 0%, so the description carries the burden. It explains pubkey as hex-encoded and compressed/uncompressed, enumerates address_type options including 'all', and clarifies network as an override of the server's network. Network values and the meaning of 'all' remain somewhat underspecified.

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 states a specific verb and resource: convert a hex public key to an address. It clearly conveys the tool's core function, though it does not explicitly distinguish it from sibling derivation tools like derive_addresses or derive_xpub.

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?

No when-to-use versus alternative guidance is provided, and no sibling tools are mentioned. 'Works offline' is the only contextual hint, but it does not help an agent choose this tool over similar derivation or conversion tools.

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