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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the safety profile is covered. The description adds useful domain context: NFH-owned, rehearsal, WETH, and openSea/mainnet exclusions. It doesn't discuss return format or pagination, but the output schema is available and this is a straight read.

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 with no wasted words. The action and target are front-loaded, and the anti-scope warning ('Never OpenSea or mainnet') is a powerful, minimal guard against misuse.

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?

For a parameterless, read-only tool with a rich output schema and clear annotations, this description covers the essential selection context: what the tool reads, whose data, and on which network. Nothing important is missing.

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?

There are no input parameters, so the schema carries no parameter burden. The description appropriately scope the operation to a fixed resource, which is the only needed parameter-related context for this tool.

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 uses a specific verb ('Read') and names the precise resource: the NFH-owned Sepolia rehearsal marketplace, including collection and WETH configuration. This clearly distinguishes it from the sibling 'get_mainnet_marketplace_status' by highlighting both the environment (Sepolia) and ownership scope (NFH-owned).

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 description gives a clear context for when to use the tool—Sepolia rehearsal marketplace config—and an explicit exclusion, 'Never OpenSea or mainnet.' It doesn't directly name an alternative tool, but the sibling list and wording make the mainnet alternative evident.

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