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

Annotations already mark readOnlyHint=true, so the description's key added value is disclosing that the response is verbatim plain text, not JSON. This is important for avoiding incorrect parsing. It doesn't cover error cases or auth, but the most significant non-obvious behavior is disclosed.

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?

Two compact sentences: the first gives the core purpose and response format, the second gives the canonical endpoint. There is no filler, repetition, or unnecessary context.

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 two-parameter read-only endpoint with full schema descriptions and explicit plain-text response disclosure, the description is nearly complete. It could mention error/not-found behavior or explicitly state that n comes from list_pings, but those are minor gaps given the schema already provides that link.

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?

Both parameters are fully described in the schema: uuid is the check's UUID and n is the ping's sequence number from list_pings. The description essentially restates these in the endpoint path and adds no further semantic detail, so it stays at the baseline for 100% schema coverage.

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?

Description states a specific action ('Get'), resource ('logged request body of a single ping'), response format ('PLAIN TEXT'), and the exact endpoint. This clearly differentiates it from sibling tools like list_pings and get_check, whose scope is different.

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 clearly implies it should be used to retrieve a single ping's request body, and the schema context points to list_pings for obtaining n. However, it does not explicitly state when to prefer this over alternatives, nor does it mention any exclusions or prerequisites.

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