test_connection

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

With no annotations, the description carries full behavioral burden. It discloses the underlying call (/me), which implies a safe, read-only, non-destructive check requiring a valid token. It does not state whether an invalid token raises an error or returns a status, nor any rate-limit or retry behavior.

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 tight sentence with the action front-loaded and the mechanism appended. Nothing wasted, nothing missing for a diagnostic check.

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 connectivity probe with no output schema and no siblings of similar kind, the description covers the essentials of what is validated. It could add one clause on expected outcome (success vs auth failure), but little else is required.

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 takes zero parameters, so there are no semantics to document; baseline 4 applies. The description correctly implies no input is needed beyond ambient configuration.

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?

States a specific verb (verify) and resource (API base URL and token), and even names the endpoint used (/me). It is unambiguously distinguishable from the invoice/customer CRUD siblings, all of which operate on business data rather than connectivity.

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?

Implied usage is clear from the wording: run it to confirm credentials and base URL before other calls. However, it never explicitly states when to use it (e.g., before first real request, after changing config) or that it is not a substitute for a data-fetching call.

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