echo

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

With no annotations, the description must disclose behavior, but it only says 'Connectivity probe.' It does not specify whether it makes a network call, echoes the message, or has any side effects. The parameter 'message' suggests echoing, but that information is in the schema, not the description. The description adds little value beyond the tool's name.

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 a short phrase 'Connectivity probe' with no wasted words. However, it is under-specified for a tool with a parameter; the brevity is not paired with necessary elaboration. It is not verbose, but it could be more informative while still being concise.

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 is simple, but the description lacks important context such as what the tool returns, how to interpret the response, or any prerequisites. Even with an output schema, the description's 'Connectivity probe' does not sufficiently prepare an agent to use the tool effectively. It should at least mention that it echoes the message back or confirms connectivity.

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 input schema has one parameter 'message' with default 'ping', but the description does not explain its meaning or usage. Since schema description coverage is 0%, the description should compensate, but it does not. The agent is left to infer from the schema alone, which reduces the description's contribution to parameter understanding.

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 states the tool is a 'Connectivity probe,' which clearly conveys its function of testing connectivity. The verb 'probe' and resource 'connectivity' provide a specific purpose that distinguishes it from the unrelated sibling tools. It is not a tautology and offers enough clarity for a simple tool.

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 guidance on when to use this tool versus any alternatives. It doesn't mention exclusions or alternative tools, and the phrase 'Connectivity probe' only implies usage indirectly. An agent would not know when to select this tool over others based solely on this description.

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