ds_test_connection

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

No annotations are provided, so the description carries the full burden. It states that the tool tests login and connectivity, but does not disclose whether this is a read-only operation, what side effects might occur, whether authentication is required, or what the response/error format looks like. This is minimal for a diagnostic tool.

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, clear sentence of six words. It is front-loaded with the verb and resource, contains no redundant information, and every word earns 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?

Given that the tool has no parameters and no output schema, the description is minimally complete for understanding its purpose. However, it does not mention the expected result (e.g., success/failure indication) or any error behavior, which would be helpful for a test/connectivity tool. It is adequate but with gaps.

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, and the schema is empty (100% coverage vacuously). Per rubric, 0 parameters gives a baseline of 4. The description adds no parameter information because there are none to describe, which 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 uses the specific verb 'Test' and clearly identifies the resource ('DolphinScheduler login and connectivity'). It is not a tautology and is clearly distinct from sibling tools, which focus on projects, workflows, resources, and other operations. There is no ambiguity about what this tool does.

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 provides no explicit guidance on when to use this tool vs alternatives. It does not mention prerequisites, exclusions, or typical scenarios (e.g., 'Run this before other DolphinScheduler operations'). The usage is only implied by the tool name and purpose.

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