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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so 'Read-only; no payment or execution side effect' largely restates structured data. It does add the useful note that no settlement or execution flow is triggered, which is relevant in a namespace containing quote_omnidome_settlement and join_omnidome, but no information on result size or shape is given.

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 front-loaded sentence with the read-only caveat appended; no filler. It is dense with unexplained domain vocabulary, but structurally efficient.

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 output schema and no parameters, the description carries the burden of telling the agent what comes back. Listing topic areas ('eight pillars', 'economic rails', 'truth boundaries') hints at content but doesn't describe the response structure, so an agent cannot predict the result format before calling.

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 disambiguate. The schema's additionalProperties=false and empty properties make the no-argument nature unambiguous.

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 verb 'Read' and the resource 'OmniDome CORE_ARCHITECTURE_V9 Planetary Bazaar' are stated, so the broad action is identifiable. However, 'eight pillars, live surfaces, roadmap targets, economic rails and truth boundaries' is domain jargon that doesn't clarify what the agent actually receives, and nothing distinguishes it from siblings like discover_omnidome_beacon, bootstrap, commons, or earn.

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 guidance on when to call this versus the many other discover_omnidome_* and read_omnidome_* tools. The reader must guess whether this is an orientation entry point or a content-specific lookup.

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