dataprobe_health

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

The disclosure of required credentials (DATAPROBE_ACCESS_TOKEN or username/password) adds operational context. However, it does not describe the response format, whether the call is read-only, or what indicates healthy vs unhealthy status, which would be useful given no annotations.

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 sentence with no redundancy. It conveys the core action and a key requirement efficiently.

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 simple health check, the description covers purpose and auth, but since there is no output schema, it should ideally mention what the tool returns. This is a noticeable gap that prevents full completeness.

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?

There are no parameters, so the description is not expected to document any. The baseline for 0 params is 4, and the description doesn't introduce any parameter-related ambiguity.

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 uses a specific verb 'Check' and a clear resource 'DataProbe service health', making the tool's purpose unambiguous. It also differentiates from sibling tools that handle datasets, questions, and SQL queries.

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 the tool is used to verify service health and states authentication prerequisites. However, it does not explicitly discuss when to use this over alternatives, though the distinction is fairly obvious from the name.

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