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

The description states the tool will 'Read registration RDAP and available ICP filing evidence', but the annotations declare readOnlyHint=false, i.e. the call is not side-effect free. That is a direct conflict on the read/write safety axis, so the safety profile an agent would infer from the text is the opposite of the declared one. The added context about disabled archive sources and no registrant PII is useful, but the contradiction dominates.

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?

Three short sentences, front-loaded with the core capability, and each subsequent sentence carries distinct information (source availability, PII posture). No filler or repetition of the tool name.

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 retrieval tool with no output schema, the description should at least define the accepted domain format and what evidence is returned (registration events, ICP filing fields, time coverage). It omits both, and its 'Read' framing conflicts with the non-read-only annotation, leaving an agent unable to predict either input form or side effects.

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 single parameter 'domain' has no schema description (0% coverage) and the description adds nothing about its expected form, such as whether a registrable domain, subdomain, or punycode/IDN value is accepted. Nothing in the text compensates for the schema gap.

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 names a specific verb and resource set: reading registration RDAP records plus ICP filing evidence for a domain. It implicitly separates itself from the analysis-oriented siblings (analyze_domain_features, analyze_domain_value, check_domain_risk, compare_domains) by retrieving raw evidence rather than producing judgements, but it never names an alternative explicitly.

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?

There is no statement of when to call this tool versus analyze_domain_features or check_domain_risk, no prerequisites, and no scenario guidance. The only contextual sentence ('additional archive sources are disabled by default until stability is verified') describes a capability limitation, not usage guidance.

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