BTCMatic agent API — discovery

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

The description lacks explicit behavioral details beyond what it does. It mentions 'Free' but does not elaborate on side effects, rate limits, or other behavioral traits. With no annotations provided, the description carries the burden, but it does not go beyond a basic overview. However, it does add context on the payment flow, which is somewhat behavioral.

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 highly concise, using a single sentence with key bullet points, and the imperative 'Call this first' is front-loaded. Every word earns its place, and it is structured effectively.

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 that the tool is a discovery/informational endpoint with zero parameters and no output schema, the description covers the essentials: what is offered, cost, bounds, and flow. It is complete enough for the agent to invoke it without further clarification.

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?

The tool has 0 parameters, and the schema is empty, so the description is the only source of meaning. It adequately explains what the tool offers given that no parameters are needed. The baseline for zero parameters is 4, and the description meets it without unnecessary details.

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 what the tool does: it provides an overview of the BTCMatic agent API, including costs, prepaid bounds, and payment flow. It distinguishes itself from siblings by positioning itself as the first call to understand the API's usage and economics.

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?

Explicitly instructs to 'Call this first,' establishing a clear ordering relative to other tools. It also sets expectations for what information will be obtained (costs, bounds, payment flow), which guides the agent on when to use it.

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