health_check

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

No annotations are present, so the description must convey behavior. It states a health check but does not detail the response format (e.g., status code, JSON) or whether it is a simple ping. Given the tool's simplicity, the lack of detail is acceptable but could be improved.

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, unambiguous sentence with no unnecessary words. It is appropriately front-loaded and earns its place.

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 has zero parameters and an output schema (implied), the description adequately covers the purpose. It does not elaborate on return values, but the output schema likely handles that. Slight improvement could mention typical response.

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, so the schema provides full coverage. The description adds no parameter information, but the absence of parameters makes this acceptable. Baseline 4 applies for no parameters.

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 'Check if the Invoicetronic API is healthy.' uses a specific verb ('check') and clearly identifies the resource ('API health'). It effectively distinguishes the tool from sibling tools that deal with invoices, companies, and events.

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 verifying API health but provides no explicit guidance on when to use versus alternative tools or any prerequisites. With many sibling tools, more context would aid decision-making.

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