check_connection

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

With no annotations, the description carries the full burden of behavioral disclosure. It discloses the core behavior (testing connection to Webull and Yahoo fallback) and the fallback mechanism. However, it does not describe what happens on failure or the exact return structure, though the output schema exists to cover return values. The fallback detail adds valuable context beyond a simple 'check connection.'

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, front-loaded sentence with no filler words. It conveys the essential action and the fallback behavior in minimal space, making every word earn its place.

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?

This is a zero-parameter connectivity check with an output schema available. The description explains the purpose and the fallback behavior, which is sufficient for the agent to select and invoke the tool. Nothing critical is missing given the low complexity and presence of output schema.

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?

There are zero parameters, so the baseline is 4. The schema coverage is vacuously 100%, and there is nothing to explain. The description correctly omits parameter details because none exist.

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 uses a specific verb 'Tests' and identifies the exact resource (connection to Webull API and Yahoo Finance fallback). This clearly distinguishes it from sibling tools that perform data retrieval, trading, or analysis operations. The purpose is unambiguous.

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 usage for verifying connectivity before relying on other tools, but it does not explicitly state when to use it versus alternatives or mention any exclusions. The implication is clear enough for a tool of this simplicity, but explicit guidance is absent.

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