Refresh the cached domain list

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and non-destructive behavior. The description adds valuable context beyond those: it refreshes a cache, avoids waiting for cache expiry, and has no upstream side effects. This is strong complementary behavioral disclosure, though it does not go into output details or potential latency.

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?

Two focused sentences deliver the core behavior, the triggering condition, and the key non-effect. There is no filler, and the most important information is front-loaded in the first sentence.

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 zero-parameter, read-only, idempotent cache-refresh operation with an output schema, this description fully covers what an agent needs to select and call it correctly. It states the trigger, the effect, the absence of side effects, and the correct sibling for listing domains.

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?

The tool has zero parameters, and the schema is fully covered with an empty properties object. Baseline for zero-parameter tools is 4; the description does not need to explain parameter meaning.

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 specifies the exact action ('re-reads the account’s domains') and the purpose (refreshing cached domain list so recent names appear immediately). It clearly distinguishes this from listing domains, pointing to eurodns_domain_search for that role.

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?

It explicitly tells the agent when to use the tool: 'right after such a change' involving a registration or transfer. It also clarifies what the tool does not do ('alters nothing upstream') and routes the actual domain listing to eurodns_domain_search, giving clear decision guidance.

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