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

Annotations already declare readOnly/idempotent/closed-world, and the description adds genuinely new behavior: result ordering (expired first, then expiring soon) and the absence of pagination. That pagination note is important operational context. It does not describe response shape beyond field names, but the ordering and non-paginated nature are the key traits.

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?

Front-loaded with the resource and scope, but the ordering rule is stated twice ('expired and expiring first' then 'Expired ones first, then those expiring soon'), wasting a sentence. The dangling filter references also add noise rather than signal.

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 one-parameter, non-paginated read tool with no output schema, the description covers contents and ordering adequately. The ghost filter parameters and lack of clarity on result volume limit its completeness for an agent planning a call.

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% for the single organization_id parameter, so a baseline of 3 would apply. But the description names domain_id and monitoring_check_id as narrowing options when neither exists in the schema, which can lead an agent to submit invalid parameters — a net negative rather than added 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?

States a specific resource (every TLS certificate in the organization) and what each entry carries: health, findings, and who renews it. No sibling tool covers certificates, so the agent can distinguish it cleanly.

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?

Offers narrowing guidance ('Narrow it with domain_id or monitoring_check_id') and notes the list is not paginated, which is useful context. However, those two filter parameters do not exist in the schema, so the guidance is partly misleading about how to narrow the query.

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