ping

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

With no annotations, the description fully discloses behavior: it calls two endpoints (public time and private account), confirms API key/secret validity, and returns three specific data points (server time, fee tier, rate-limit budget). This goes well beyond a simple 'ping' and gives the agent a clear picture of side effects and response content.

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 three succinct sentences, front-loaded with the primary purpose. No redundant wording; each sentence adds unique value (purpose, method, outputs).

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 or annotations, the description is remarkably complete. It explains what the tool does, how it works, and what it returns, covering all necessary context for an agent to invoke and interpret results.

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 zero parameters, so the schema carries no semantic burden. The description adds context about what the tool does (endpoint calls, returned values), but since there are no parameters to explain, the baseline 4 is appropriate.

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's function: 'Verify the connection and credentials against Bitvavo.' This is a specific verb (verify) with a resource (Bitvavo connection/credentials), and it is clearly distinct from sibling tools that retrieve market or account data.

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 implies the use case: check connectivity and credential validity before relying on other tools. It does not explicitly contrast with alternatives, but the sibling tools are all data-retrieval functions, making the diagnostic purpose evident.

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