test_connection

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

No annotations are provided, so the description carries full responsibility for disclosing behavioral traits. It only states 'Test Mattermost connection' without revealing whether the operation is read-only, whether it makes network requests, or what the return value signifies. The agent cannot infer side effects or expected outcomes from this minimal description.

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 extremely concise, consisting of three words, and every word is necessary. It is front-loaded with the action and resource, with no superfluous content. For a simple zero-parameter tool, this is appropriately sized.

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 has very low complexity: no parameters, no output schema, and a simple purpose. However, the description does not clarify what the tool returns (e.g., success/failure) or any behavioral details needed to interpret results. It is sufficient for basic intent but leaves a gap in expected response handling.

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?

With zero parameters, the baseline is 4. The schema already fully documents the empty parameter structure, and the description adds no new information about parameters because there are none. No compensation is needed.

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 'Test Mattermost connection' uses a specific verb and resource, clearly indicating it verifies connectivity to Mattermost. It distinguishes itself from sibling tools like get_thread, send_message, and search_posts by focusing on connection status rather than data operations.

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 checking connectivity but offers no explicit context on when to use it versus alternatives or when not to use it. Its purpose is unambiguous enough that an agent can infer appropriate use, but guidance on prerequisites or fallback options is absent.

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