rabbitmq_broker_check_certificate_expiration

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It lacks details on whether the tool is read-only, what happens if no certificates expire, required permissions, or any side effects. Minimal behavioral context is given beyond the basic function.

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 short (two lines) but front-loaded with the main purpose. However, the repetition of 'unit:' and the lack of structured formatting reduce conciseness. Every sentence earns its place, but more detail could be added without making it overly long.

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?

Given no output schema and no annotations, the description is incomplete. It tells what the tool checks but not what the response looks like, how to interpret results, or any constraints. For a 2-parameter tool, the description could provide more context to fully inform usage.

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 coverage is 0%, so the description must add meaning. It explains 'unit: days, weeks, or months' for the unit parameter, but does not explicitly describe the 'within' integer parameter (though 'within the given timeframe' implies it). The added value is partial, but the schema defaults provide some guidance.

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 clearly states 'Check if any TLS certificates expire within the given timeframe,' specifying the verb (check), resource (TLS certificates), and scope (expiration within timeframe). It distinguishes itself from sibling check tools like rabbitmq_broker_check_local_alarms by focusing 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 vs alternatives. There is no mention of prerequisites, context for usage, or when not to use it. The description only states what it does, leaving the agent to infer usage.

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