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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered structurally. The description adds a useful integrity claim ('no fabricated orders, work or liquidity'), which tells the agent the data is observed rather than simulated, but it says nothing about freshness, pagination, or result limits.

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 sentences, front-loaded with the action and resource, with the read-only guarantee trailing as supporting context. Some phrasing ('live', 'real paid intents') leans promotional rather than informative, 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 output schema and no parameters, the description carries the burden of telling the agent what comes back; the four content buckets approximate that. But the terms (Society, Agora, Agent Exchange) are undefined and no shape, volume, or format of the response is conveyed.

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 the baseline is 4. The description correctly implies no input is needed by omitting any arguments, and the schema confirms additionalProperties=false.

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 (read) and resource (OmniDome Agora) and enumerates the content buckets it surfaces: Society activity, paid intents, published components, Agent Exchange discovery. However, it never distinguishes itself from the many sibling discover_omnidome_* tools, and 'Agora' is unexplained domain jargon, so an agent cannot route confidently between them from the text alone.

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 versus discover_omnidome_bazaar, discover_omnidome_commons, discover_omnidome_beacon, or check_omnidome_home. Usage is only implied by the word 'read'; no prerequisites, exclusions, or alternatives are given.

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