Server — Ping

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

Annotations already declare readOnlyHint/openWorldHint/destructiveHint, but the description adds behavior those annotations cannot convey: zero API calls, no token validation, no budget read, and the deliberate quota-free design intent. It also previews the payload (version, whether write tools are registered, request budget), which is real disclosure beyond structured fields.

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?

Front-loaded with the [READ] tag and the core question, then rationale and return contents. The rate-limit rationale sentence is longer than strictly necessary, but it is the tool's raison d'être and each sentence carries information.

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 zero-parameter ping with an output schema, the definition supplies everything an agent needs: what it does, why it exists, its cost profile, and a preview of the return. Nothing material is missing.

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 zero parameters and 100% schema coverage, so the baseline is 4. The description correctly treats this as a no-argument call and spends no words on non-existent parameters.

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?

States a specific verb and resource — a health/ping check on the server — and immediately scopes it ('answers from the process alone'). It is clearly distinguishable from data-reading siblings like overview_request_budget or transactions_list because it explicitly performs no YNAB request, token check, or budget read.

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?

Gives a concrete when-to-use scenario: an agent that has been rate limited and needs a reachability check that does not spend quota or fail for unrelated reasons. It effectively describes when-not-to-use (anything that touches the API/token). It stops short of naming a specific alternative sibling, so it is clear context rather than full routing.

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