countExpiringDomains

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

With no annotations, the description carries the burden; it clearly states the scoped read-only behavior ('domains in the account') and the filtering window. It does not explicitly state the return shape or whether expiring boundaries are inclusive, and only points to an external API reference for those details.

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?

A single sentence that front-loads the action and resource, with the condition and a reference link. There is no filler or redundant wording.

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 count operation with full schema coverage, the description covers the essential call context. The API reference link mitigates the lack of an output schema, though a brief statement that the response is just the count would make it fully self-contained.

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%, so the parameter `daysCount` is already described as a 'look-ahead window in days'; the description repeats this as 'N days' but adds no new format or constraint information beyond the schema.

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 uses a specific verb ('Count') and resource ('domains in the account') with an explicit expiration condition, so the operation is clear. It does not explicitly distinguish itself from listExpiringDomains, but the 'Count' wording makes the aggregation intention apparent.

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 intended use is implied: call this when a numeric count of soon-expiring domains is needed, while listExpiringDomains exists for listing details. However, there is no explicit when-to-use/when-not-to-use guidance or named alternative, so the agent must infer the choice.

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