ping

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

With no annotations, description fully discloses authentication (API key), concurrency limit (Max 10), read-only nature, error handling (returns error for invalid/missing key), and return format (health_check and status_code).

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?

All sentences are valuable: purpose, usage, behavior, return. Front-loaded with core action. 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?

Covers everything needed: purpose, usage, behavior, auth, limits, return values. Given zero params and simple output, description is complete.

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?

No parameters exist, so schema coverage is 100%. Description implicitly confirms no inputs needed. Baseline for 0 params is 4; description adds no extra param info but that's acceptable.

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?

Clearly states 'Check API connectivity and verify the API key is valid', which is a specific verb+resource. Distinguishes from sibling tool get_account_info by explicitly saying to use that for account details.

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?

Explicitly says 'Fastest health check available' and advises using get_account_info for account details. Also notes it is safe to retry, providing clear when-to-use guidance.

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