wikijs_connection_status

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

With no annotations provided, the description carries the full burden of behavioral disclosure. 'Test' and 'get' imply a read-only, non-mutating operation, which is helpful, but the description does not mention failure behavior, network dependency, or what specifically happens if the connection is unavailable. For a zero-parameter status tool, this is minimally adequate but not rich.

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 concise sentence that states both the primary action and the expected result. Every word contributes value, and there is no redundant filler or repetition of the tool name.

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 the tool's low complexity, zero parameters, and lack of annotations or output schema, the description is mostly sufficient for an agent to understand the purpose and invoke it correctly. It could be more complete by specifying what 'basic site information' includes, and by clarifying how this differs from wikijs_get_site_info, but these are minor for a simple connection test.

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 trivially fully covered, so there are no parameter semantics for the description to clarify. Baseline for zero-parameter tools is 4, and the description does not introduce any conflicting or unnecessary parameter-related information.

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 clearly states a specific verb ('Test') and resource ('connection to Wiki.js'), and adds that it retrieves basic site information. It is distinguishable from siblings primarily through the 'connection status' framing, but it does not explicitly differentiate itself from wikijs_get_site_info, which likely overlaps in the 'basic site information' part.

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?

There is no guidance about when to use this tool versus alternatives such as wikijs_get_site_info, wikijs_workspace_status, or wikijs_repository_status. The description implies it is a connection health check, but it never states this should be used first or that it should be preferred over sibling tools for connectivity validation.

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