test_connection

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

No annotations are provided, so the description must fully disclose behavior. It mentions retrieving the default account balance as part of the test, but does not state whether this is a read-only operation, what happens on authentication failure, or the expected return format. This leaves important behavioral aspects undisclosed.

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 a single, concise sentence that front-loads the primary purpose ('test the connection') and clearly explains the verification method. No unnecessary words or repetition.

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?

The tool is simple with no parameters and no output schema. The description conveys the core purpose but does not explain the return value, error handling, or what 'selected default account' specifically refers to. This is a moderate gap for a connectivity test, but the description is minimally sufficient for basic understanding.

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 there is nothing to explain. According to the rubric, a baseline of 4 is appropriate for tools with no parameters, and the description does not need to add parameter information.

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: testing the connection to the TropiPay API and verifying authentication. It uses specific verbs ('test', 'verify') and identifies the resource (API, authentication). It distinguishes itself from sibling tools like get_default_account_balance by focusing on connectivity rather than just returning a balance.

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 this tool is used when you need to test the connection or verify authentication status. It provides clear context for when to use it, but does not explicitly mention alternatives or exclusion scenarios (e.g., when to use get_default_account_balance instead). Thus, it has clear context but lacks exclusions.

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