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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so safety is covered. The description adds genuinely new behavior: the result set is paginated and each item returns slug, name, supply and identifiers, which tells the agent what to expect from a call.

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 compact sentences with no filler; the purpose and pagination constraint are front-loaded, and the routing hint to sibling tools comes second where it belongs.

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?

No output schema exists, and the description compensates by naming the returned fields (slug, name, supply, identifiers) and the paginated nature of the response. Complete enough for a simple list tool, with only minor gaps such as total page counts or item ordering.

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?

Schema coverage is 100% and the single 'page' parameter is fully documented in the schema, including the 1-indexed convention and omitting it for the first page. The description only echoes the pagination concept, adding nothing beyond the structured field, so baseline 3 applies.

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 and resource ('Browse all indexed Bitcoin Ordinals inscription collections') plus the scope qualifier '(paginated)', and names the sibling tools it is not (getCollectionInfo / getCollectionMarketInfo). An agent can distinguish it from the many other collection tools without opening a schema.

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?

Explicitly positions the tool as a discovery step and routes the agent to getCollectionInfo / getCollectionMarketInfo for floor price and asset detail. It gives clear when-to-use context but no explicit when-not-to-use or exclusion, so it stops just short of a 5.

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