healthcheck

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

No annotations are provided, so the description bears the full burden for behavioral disclosure. It does not state whether the tool is read-only, what permissions are needed, or whether it has side effects. The phrase 'read-only identity' suggests a check for read-only status but does not explicitly confirm the tool itself is non-destructive.

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 sentence that front-loads the action ('Check') and enumerates the specific items checked. It contains no extraneous words and is efficiently structured for quick comprehension.

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?

The description lists what is checked but omits context such as the purpose of the healthcheck, what 'read-only identity' entails, and when an agent should invoke it. An output schema exists, so return values are covered, but the description remains somewhat minimal for a diagnostic tool.

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 sole parameter, request_id, is fully described in the schema as an optional audit request ID. The description adds no extra meaning about this parameter, but with 100% schema description coverage, the baseline of 3 applies.

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 begins with the specific verb 'Check' and names precise resources: 'PostgreSQL, yrb3_v3 tables, read-only identity and current row counts.' This clearly distinguishes it from the sibling evidence/search tools by indicating a health-monitoring purpose rather than data retrieval.

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?

No guidance is provided on when to use this tool versus alternatives or exclusions. The description only states what it checks, leaving usage entirely implied. There is no mention of conditions like 'run before other queries' or 'use for diagnostics.'

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