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

Annotations already declare readOnlyHint=true, so the safety profile is largely carried by structured data; the description redundantly confirms 'zero side effects' but adds value with the X-License-Key authentication requirement, which is nowhere in the annotations or schema. It does not mention rate limits, latency, or cost, which keeps it short of a 5.

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 sentences, front-loaded with the capability, then usage, then exclusions and auth—good ordering with no wasted preamble. The only blemish is that 'contradiction alarms' appears twice (in the returns list and again in the use cases), a small redundancy.

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?

An output schema exists so return values need no prose, annotations cover the read-only profile, and the description still supplies the auth prerequisite and the boundary against content-query siblings. Everything an agent needs to choose and invoke this tool is present.

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 description coverage is 100% and the single optional space_id parameter already documents that it defaults to the caller's 'default' space. The description never mentions space_id, so it adds no meaning beyond the schema; baseline 3 applies.

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 verb ('audits and returns real-time diagnostic telemetry') against a specific resource ('partitioned memory space') and enumerates the concrete metrics returned (node counts, synapses, grounded facts, contradiction alarms). An agent can distinguish this from icx_recall_scoped, icx_quote_slot, and icx_inspect_connector_facts without opening any schema.

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?

Gives four concrete positive use cases (monitor partition health, verify ingestion, check capacity, detect contradiction alarms) and an explicit exclusion naming the two alternative tools for content retrieval. Both the when and the when-not are stated, with the alternative tools named.

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