Return satoshidata.ai's free Bitcoin wallet trust and safety teaser for a single address, including the examined marker when no clear category matched.
| Name | Required | Description | Default |
|---|---|---|---|
| address | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
| ok | Yes | ||
| data | No | ||
| error | No | ||
| endpoint | Yes | ||
| status_code | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries full burden. It notes that the tool returns a 'teaser' and mentions an 'examined marker' behavior, providing some insight. However, it lacks details on authentication, rate limits, or other behavioral traits, leaving gaps.
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?
One sentence, no unnecessary words. Every part contributes to the purpose. Efficient and front-loaded.
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 the tool has only one parameter and an output schema, the description covers the basic functionality. However, it does not explain how it differs from many similar sibling tools, making it less complete for an agent to decide when to use it.
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 must compensate. It implies the parameter 'address' is a single Bitcoin address, but provides no format constraints or additional meaning beyond the schema. This is minimal added value.
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 returns a 'Bitcoin wallet trust and safety teaser' for a single address, including a specific marker when no clear category matched. It uses a specific verb and resource, but does not explicitly distinguish it from sibling tools like address_risk or address_intelligence.
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 guidance on when to use this tool versus alternatives. The description does not mention context, exclusions, or compare to other tools, leaving the agent without direction for appropriate usage.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Multiple tools cover similar address intelligence (e.g., address_intelligence, address_risk, risk_check, wallet_summary) and dormant coin detection (pulse_dormant, dormancy_flushes, chain_awakenings), causing potential confusion despite descriptive names. Some overlap exists but descriptions help differentiate.
Tools use snake_case and generally follow a verb_noun or noun_verb pattern (e.g., address_evidence_pack, batch_intelligence, fees_recommended). However, a few tools like submit_feedback and verify_timestamp start with verbs, while others start with resources, causing minor inconsistency.
44 tools is high for a wallet intelligence server, covering many subdomains (address, batch, blockchain, mempool, mining, timestamping, etc.). While each tool has a specific purpose, the count feels heavy and could be consolidated, but it's not extreme given the broad scope.
The tool set thoroughly covers Bitcoin wallet and on-chain intelligence: address lookup, risk, evidence, batches, blocks, mempool, fees, mining pools, timestamping, transaction broadcast/verification, pulse feeds, whales, and more. No obvious gaps for the stated purpose.