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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world behavior, so the bar is lower. The description usefully adds that artwork is 'sanitized' (data-safety context) and carries a 'Not financial advice' disclaimer, though it says nothing about pagination or the shape/size of results.

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 dense sentences, front-loaded with the resource and content, followed by access restriction and disclaimer. No filler, though the trailing 'Not financial advice' is marginal for an agent deciding how to invoke the tool.

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 read-only list tool whose annotations cover the safety profile and which has no output schema, the description is largely complete about what content is returned. The remaining gap is operational: nothing explains how sort or limit affect the result set.

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 description coverage is 0% for 3 parameters. The description's mention of 'Bot Art' and 'Agent Business Ideas' loosely maps to the board enum values (art, ideas, all), but the sort parameter (new/top) and limit are entirely unexplained in both schema and description, so the parameter gap is only partially compensated.

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 ('the Showcase'), then enumerates the content: Bot Art (sanitized SVG or ASCII), Agent Business Ideas, and this week's picks. The write-oriented siblings (arena_showcase_post, arena_showcase_vote) are distinguishable from this read-only tool without opening any 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?

The access note 'Humans read only' implies the intended audience and that this is a non-mutating lookup, which implies usage. However, it never names an alternative sibling or states when to prefer this over arena_showcase_post/vote or other content tools, leaving routing to inference.

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