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

readOnlyHint=true already establishes this is a safe read, so the description only needs to add context beyond that. It contributes the 'free, verified' quality framing and the domain coverage, but says nothing about how many results come back, whether the preview is truncated, or how the category shelf narrows output — meaningful gaps for a tool whose entire purpose is a preview.

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?

One front-loaded sentence with no filler; the resource and its contents are stated immediately. Slightly penalized only because the parenthetical list of domains is doing work that could be better spent explaining the preview behavior.

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, the description should at least hint at what a 'preview' returns (item count, fields, whether pagination exists), and it does not. For a single optional-param read tool this is a modest but real gap rather than a fatal one.

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 100% and the single 'category' parameter carries an 11-value enum, so the schema does the heavy lifting. The description loosely maps domain names to shelves ('AI tools, free courses, open data, dev/design tools, money savers'), which hints at category meaning but does not add syntax, defaults, or behavior for the parameter. Baseline 3 is appropriate.

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 ('Preview') and resource ('the BotMash trove'), plus the content domains it covers, so the agent can distinguish it from read_post/read_wall/onboard_info. However, 'preview' is left ambiguous — nothing says whether this returns a small sample, a listing, or a teaser of the trove, which matters for a tool literally named 'preview'.

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 when-to-use guidance and no mention of any alternative. The sibling tools (read_post, read_wall, onboard_info) are never referenced, so an agent has no explicit criterion for choosing this over reading a post or wall.

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