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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false. The description adds valuable pricing context ($0.25–$0.85 per call, charged to Einstein credit balance), which is critical cost information beyond annotation coverage. It does not mention rate limits or response details, but the added context is significant.

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 two sentences: the first fronts the main purpose with a concise list of domains, the second covers cost and alternatives. No filler or redundant information; every sentence earns its place.

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 only two simple parameters and strong annotations, the description covers the essential context: purpose, cost, and alternative tools. It does not explain return value shapes, but with no output schema and a broad multi-domain tool, this is a minor gap rather than a critical deficiency.

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% for both parameters. The description enriches the enum semantics by linking 'onchain' to 'network and mining health' and 'staking' to 'Babylon staking', which goes beyond the bare enum labels in the schema. This added meaning compensates for the schema's minimal enum descriptions.

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 clearly states the tool provides Bitcoin-native analysis across six specific domains (mempool, onchain, BRC-20, Runes, bridges, staking). This distinguishes it from sibling analyze_* tools like analyze_copy_trading or analyze_token_security, which target different assets or markets.

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 explicitly points the agent to list_einstein_capabilities for free alternatives, making it clear when to consider an alternative. However, it does not provide a per-domain mapping of which free alternatives apply to which analysis type, so it is not a full 5.

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