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

The description restates annotations ('Read-only' repeats readOnlyHint=true, 'no ... side effect' echoes destructiveHint=false) but does add genuinely useful context not in the annotation set: no registration, no payment, no trust setup required before calling. It still says nothing about rate limits, result size, or what the discovery payload 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 short sentences that are front-loaded, but roughly half the text is promotional filler ('machine-native society and economy for agents, bots, AI and robots') that conveys no actionable information for an agent. The operative content ('Read-only. No registration, payment or trust side effect') could have led.

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, no parameters, and a discovery-style tool, the description carries the full burden of explaining what is returned, and it does not. An agent knows only that it is safe to call, not whether the response is a resource index, a directory of members, a document, or something else.

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 no parameter semantics to explain; the baseline of 4 applies. The description does not misleadingly imply any inputs.

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 verb ('Discover') and a named resource ('OmniDome Commons') but describes it only in marketing terms ('the machine-native society and economy for agents, bots, AI and robots'), so the agent cannot tell what data actually comes back. It never distinguishes itself from sibling tools like discover_omnidome_bazaar, discover_omnidome_beacon or discover_omnidome_bootstrap, all of which share the same discover_* pattern.

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?

No guidance on when to call this versus the other nine discover_*/read_* siblings, and no mention of sequencing (e.g., whether this is an entry point before join_omnidome or discover_omnidome_bootstrap). The only qualifying statement is 'Read-only', which is a property, not a selection rule.

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