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

With no annotations, the description carries the full behavioral burden. It explicitly discloses the output contents, the ordering, the 30-day highlight, and the sign-in requirement, making the tool's behavior transparent for a read-only overview. It does not cover edge cases like empty results or error handling, but that's acceptable for a zero-param read tool.

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 exactly two sentences: the first lists the output features, the second states the auth requirement. No fluff, and the main action is front-loaded.

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 the tool's simplicity (zero parameters, no output schema, no annotations), the description provides a comprehensive overview: purpose, output specifics, and prerequisites. It could be slightly more detailed about the exact return structure, but it's sufficient for an agent to correctly invoke the 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?

There are zero parameters, so the schema is empty and the baseline is 4. The description adds no parameter semantics but correctly notes the sign-in requirement as the only prerequisite, which is not a parameter.

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 it retrieves an SSL certificate expiry overview for monitored domains, with specific output details (per-alert-level counts, sorted certs, 30-day highlight). This distinguishes it from sibling tools like ssl_certificate or my_overview by focusing on certificate expiry across the user's monitored set.

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 implies usage for reviewing certificate statuses across monitored domains, and notes the sign-in prerequisite, but it does not explicitly state when to prefer this over ssl_certificate or other alternatives. No exclusions or when-not-to-use guidance is provided, so it only reaches the 'implied usage' level.

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