ping

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

The description discloses return behavior: returns an error object if key is invalid/missing, and outlines the return JSON. The annotations (readOnlyHint=true) already indicate a safe read operation, and the description adds context about error handling and return format without contradicting 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 brief, uses bullet points for return info, and every sentence adds value: purpose, usage hint, error behavior, return format. No unnecessary words.

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 tool with an output schema, the description covers purpose, usage guidance, and return format. The only gap is the undocumented optional parameter, which for a 'ping' operation may be minor but still incomplete.

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 schema has one optional parameter 'account' with no description (0% coverage), and the tool description does not explain its purpose or effect. The description fails to add any meaning beyond the schema, leaving the agent uninformed about this parameter.

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 checks API connectivity and validates API keys, using the specific verb 'check' and resource 'connectivity/key validity'. It distinguishes itself from the sibling tool 'get_account_info' by noting that is for account details, making its purpose distinct.

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 explicitly says it is the 'fastest health check available' and advises using 'get_account_info instead if you need account details', providing clear context for when to use this tool versus an alternative.

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