health

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

No annotations are provided, so the description carries the full burden. It discloses that probes are 'bounded cached', implying safe execution, but does not describe default behavior when probe=false, potential side effects, return format, or whether the operation is read-only. This is minimal behavioral disclosure for a tool with zero annotation support.

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 efficiently front-loads the tool's purpose and then clarifies the parameter behavior. Every word contributes to meaning, with no unnecessary elaboration.

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 one-parameter tool with an output schema, the description covers the core purpose and parameter semantics. However, it lacks explicit usage guidance and default behavior context, making it minimally complete but not thorough.

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 input schema only defines a 'probe' boolean with a default. The description adds meaning by explaining that setting probe=true triggers 'bounded cached probes', clarifying the effect of the parameter. This goes beyond the schema's bare title and default value.

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 states 'Provider configuration and circuit health', which clearly indicates the tool's purpose as a health-check resource. It differentiates from sibling tools 'search' and 'fetch' by focusing on health rather than data retrieval, though it lacks an explicit verb like 'get' or 'check'.

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 mentions 'probe=true runs bounded cached probes', which gives guidance on using the optional parameter but does not explicitly state when to use this tool versus alternatives. The usage context is implied as a health check, but no exclusions or alternative tool references are provided.

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