Get ssl and domain expiry

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

Annotations already establish readOnly/idempotent/non-destructive, so the bar is lower; the description still adds substantive behavior: a null date means Staygreen has no date and 'never guesses one,' plus follow-next_cursor pagination guidance. It stops short of stating result shape or size limits, which keeps it below a 5.

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?

Four tight sentences with no filler, front-loaded with what it returns and immediately followed by scoping, alternative routing, and pagination. Each sentence carries distinct, actionable 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?

An output schema exists so return-value detail is unnecessary, and the description covers the remaining agent-critical points: scope semantics, null-date handling, sibling routing, and pagination. Nothing needed to invoke it correctly 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?

Schema coverage is 100%, giving a baseline of 3, but the description adds real semantics beyond the schema: omitting app means every SSL monitor in the workspace versus passing an app id for that app's hosts only. The cursor sentence reinforces the paging contract in practical terms.

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+resource ('Read certificate and domain expiry dates, with days remaining') and scopes it to monitored hosts. It also names the sibling it is not (get_status) so the agent can discriminate without opening either schema.

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?

Explicitly gives the selection rule: 'Use this for renewal deadlines; use get_status instead for whether a site is up now.' It also spells out the app-or-not branching, so an agent knows exactly when to omit or pass the app parameter.

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