taproot_get_pubkey

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

With no annotations, the description carries the burden well by disclosing the active-wallet scope, the exact derivation path, the 32-byte hex output, and the requirement that the wallet be unlocked. It does not explicitly state that the operation is read-only or describe failure behavior, but it covers the key behavioral traits needed to invoke it.

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 sentences are front-loaded and efficient: what is derived, how, and the unlock prerequisite. However, the final tip about `earning_opportunities` is unrelated to selecting or invoking this tool and does not earn its place in the definition.

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 zero-parameter tool with no output schema, the description is complete enough: it explains the derivation source, exact path, output encoding, and auth prerequisite. An agent has enough information to call it correctly and interpret the result.

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?

This tool has zero parameters, so parameter semantics are minimal by design. The description appropriately avoids inventing parameter details and instead focuses on output format and derivation path.

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 gives a specific verb and resource: derive the x-only Taproot public key from the active wallet. It also states the output format and exact BIP-86 derivation path, which distinguishes it from address-oriented or multisig-verification siblings.

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?

It clearly states the use case: share the pubkey with co-signers to construct a Taproot multisig script tree. It also gives the prerequisite to unlock the wallet first, though it does not name when-not-to-use conditions or explicit alternatives.

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