get-health-certificate-expiration

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

Annotations declare readOnlyHint=true, so the description aligns by stating 'Get health check status'. However, it does not elaborate on what the status means, or any behavioral traits such as rate limits or authorization needs. The openWorldHint adds context but the description adds little beyond that.

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, which is concise but too short to be informative. It lacks structure such as parameter explanations, and the brevity comes at the cost of completeness, making it under-specified.

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?

Despite the low complexity (2 parameters, no output schema), the description does not explain the return format or the meaning of 'health check status'. It also fails to clarify how the parameters work together, leaving the agent with insufficient information to use the tool correctly.

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?

Schema description coverage is 0%, and the description only mentions 'within a given time' without explaining the 'within' and 'unit' parameters. No examples, allowed values, or format guidance are provided, leaving the agent unclear about how to specify the time range.

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 specifies 'Get health check status for certificate expiration', clearly indicating the resource and action. It distinguishes from other health check sibling tools like get-health-alarms, as it focuses on certificate expiration.

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 other health check tools or alternatives. The description does not mention prerequisites, exclusions, or context for usage.

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