aircall_ping

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

Annotations already declare readOnlyHint=true, so the safe, read-only nature is known. The description adds that it tests 'connectivity and credentials,' which is useful context beyond the annotation. However, it does not disclose details about the response format or potential errors, which is relevant for a connectivity check, though not critical for a simple ping.

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 two concise sentences: the first states the core function, the second provides usage context. Every word earns its place, and the purpose is immediately clear. No redundancy or filler is present.

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 extremely simple with no parameters and a clear purpose. The description covers the essential context: what it does and when to use it. While it could mention the nature of the response (e.g., success/failure indication), the lack of an output schema and the trivial nature of a ping tool make this a minor gap. Overall, the description is sufficient for an agent to invoke and interpret the result at a basic level.

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 description is not required to explain parameter semantics. The schema coverage is effectively empty, and the baseline for a 0-parameter tool is 4. The description appropriately focuses on the tool's purpose without unnecessary parameter details.

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: 'Test connectivity and credentials against the Aircall API.' It uses a specific verb and resource, and the 'Use this to troubleshoot the connection' further clarifies its intent. This distinguishes it from all sibling tools, which focus on data operations rather than connectivity checks.

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 a clear when-to-use instruction: 'Use this to troubleshoot the connection.' It does not explicitly mention alternatives or when not to use it, but given its unique diagnostic purpose, this is sufficient context for an agent to select it appropriately.

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