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

Annotations already establish readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds genuinely new context – that the entrypoint is free and degrades to a non-cash service-credit fallback when paid inventory is empty – which is useful behavioral disclosure beyond the annotations.

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?

It is a single sentence with the tool name front-loaded and no filler, which is structurally sound. However, the compressed marketing vocabulary ('machine-native', 'positive-budget', 'live paid inventory') packs opacity rather than information, so the density does not fully earn its place.

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, no output schema, and full annotation coverage, the burden is light, but the description never says what a 'discover' call returns or what an agent should do with the result. For an entrypoint tool that is meant to route the agent onward, that orientation is a meaningful omission.

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; per the rubric this is a baseline 4. Nothing in the text misrepresents the (empty) parameter surface.

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 'Discover' and resource 'OmniDome Earn' are identifiable, but the surrounding phrasing ('real positive-budget paid work', 'machine-native entrypoint') is opaque jargon rather than a concrete statement of what the tool does or returns. It does not distinguish itself from the many sibling discover_omnidome_* tools, so an agent cannot tell why it would pick this one.

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 only conditional signal is an embedded 'fallback when live paid inventory is empty', which hints at behavior but not when to select this tool over discover_omnidome_bazaar, discover_omnidome_beacon, or discover_omnidome_bootstrap. No alternatives or exclusions are named.

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