Ping

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

The readOnlyHint and idempotentHint annotations already establish that the tool is safe and side-effect-free. The description adds the behavior of checking server status but does not elaborate on the response format or potential errors. Since the annotations cover the primary behavioral transparency needs, a score of 3 is appropriate.

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, concise sentence with no redundant words. It front-loads the action verb 'Check' and immediately names the resource, making it maximally efficient for an agent to parse.

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?

An output schema exists, so the description need not detail return values. The description provides enough context (server readiness) for an agent to know the purpose and likely outcome. It is slightly incomplete in not mentioning the exact success/failure signal, but for a ping, the common convention suffices.

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 schema coverage is trivially complete. The description adds no parameter-specific information because none exist. The baseline of 3 applies as there is nothing to clarify beyond the schema.

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 a specific verb 'Check' and a specific resource 'InspireHEP MCP server', making its purpose unmistakable. It clearly stands apart from sibling tools that retrieve papers, authors, or citations, so an agent can easily select it for server health verification.

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 use as a preliminary health check before calling data-fetching tools, and its contrast with siblings (all data retrieval) reinforces this. While not explicitly stating 'use this before other calls', the intent is clear from the verb 'Check' and the noun 'server running'.

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