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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description nonetheless adds genuine context by enumerating what will NOT happen (no installation, registration, payment, or third-party runtime side effect), which usefully separates it from join_omnidome and the settlement tools. It stops short of saying what the response actually contains.

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 tight sentences with the operation stated first and the safety contract second; no filler. The dense noun phrase "zero-client bootstrap and opt-in propagation contract" costs some readability, but nothing is wasted.

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?

With no parameters and rich annotations, most of the burden is lifted, but there is no output schema, so the description is the only hint at what the read returns — and "bootstrap contract" does not tell an agent whether it gets a document, a config blob, or instructions. Adequate but with a clear informational gap for an entry-point tool.

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 takes zero parameters, so there is nothing for the description to document beyond confirming it is a no-argument read — the baseline for a parameterless tool. No schema-level ambiguity exists to compensate for.

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 ("Read") and a specific named artifact ("OmniDome CORE_ARCHITECTURE_V10 zero-client bootstrap and opt-in propagation contract"), so the action is unambiguous. It does not differentiate itself from the many sibling discover_omnidome_* tools, and the artifact name is jargon-heavy enough that an agent can't fully picture the content.

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 term "bootstrap" implies this is the entry point to call before the other OmniDome tools, but that is left implicit — there is no explicit "call this first" or "use X instead when Y" routing. No prerequisites or exclusions are stated, even though nine sibling tools compete for the agent's selection.

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