dts_ping

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

No annotations are present, so the description carries the full burden. It discloses what the tool does (checks installation/reachability), what it reports (Engine version, executables, bundled GDAL), and its critical dependency behavior (other tools fail without it). Lacks detail on error handling or return format, but for a simple ping this is substantial transparency.

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 three sentences long and every sentence adds value: purpose, usage instruction, and what is reported/dependency. No wasted words, and it is front-loaded with the primary action.

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 simplicity (no parameters, no output schema), the description fully captures what an agent needs: the purpose, when to call, what output information to expect, and the critical dependency context. It is complete for selecting and invoking the tool correctly.

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 no parameters, and the input schema is empty. Per the rubric, a baseline of 4 applies when there are 0 parameters. The description adds no parameter info needed, since there are none to explain.

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 the tool's function: 'Check that DTS Engine is installed and reachable.' It uses a specific verb (check) and resource, and distinguishes itself from siblings by positioning it as a first-step prerequisite ('Call this first', 'Every other tool fails if this one 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?

Explicit guidance is provided: 'Call this first' and 'Every other tool fails if this one does.' This makes it clear that the tool should be used before all other sibling tools, and implies it is a gate for the rest. This is strong when-to-use guidance even without naming alternatives.

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