finance_test_connection

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

With no annotations provided, the description carries the burden of behavioral disclosure. It signals a non-mutating connectivity and credential verification across three named integrations, which is sufficient for a zero-parameter check tool. It does not discuss partial-failure behavior, but an output schema exists to cover result details.

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?

A single sentence front-loads the action and names all three target systems with no filler or redundant wording.

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 aggregate connectivity check with an output schema, the description covers the needed scope and intent. The only minor gap is that it does not explicitly compare itself to the individual test_connection siblings, though that is easily inferable from the tool names and context.

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 input schema fully covers parameter semantics. The baseline of 4 applies because there is no parameter information the description would need to add.

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 states a specific action ('Check'), the exact resources (DART, Toss, Telegram credentials/connectivity), and the combined nature ('in one call'), which clearly distinguishes it from the per-service sibling tools like dart_test_connection and toss_test_connection.

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 phrase 'in one call' clearly communicates that this is the aggregate connectivity test, so an agent can infer when to choose it over the individual test_connection tools. It does not explicitly name alternatives or state exclusions, but the context is clear enough.

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