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

The annotation only says readOnlyHint=true and openWorldHint=false. The description goes well beyond that by explaining the x402 payment requirement, the PaymentRequired result for unpaid calls, retry with _meta['x402/payment'], verification/execution/settlement flow, and the fail-closed behavior. These are critical operational behaviors the structured metadata did not cover.

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 front-loaded with a clear purpose, then gives usage guidance, and then payment details in a relatively compact form. But the repeated 'MISSING' placeholder and the flourish 'canonical Kappa financial engine' make the text less crisp and distract from the concrete, useful guidance.

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 single-parameter, read-only lookup tool with a fully documented input schema, the description is largely complete. It explains the unusual paid-tool behavior and failure semantics, which are essential. It does not describe the shape of the returned metadata, but because there is no output schema and the lookup is standard, this is a minor 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 100% and the only parameter, username, is already described with an example. The description simply calls the lookup a 'public GitHub user metadata' lookup, which only subtly hints at the username parameter and adds no parameter syntax or format details 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?

The description states a clear verb and resource: 'look up public GitHub user metadata.' It also tells the agent not to call list_verified_capabilities or search_verified_capabilities first, which differentiates it from those capabilities. However, the phrase 'direct MISSING tool' includes an unexplained placeholder that muddies the exact identity of the tool.

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 gives explicit routing guidance: 'Prefer this tool when the caller's task matches this capability; do not first call list_verified_capabilities or search_verified_capabilities.' This clearly tells the agent when to call this tool directly and which sibling capabilities to avoid.

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