random

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

With no annotations, the description carries the full behavioral burden. It does disclose the return shape ('title + summary + thumbnail') and language support, which is useful. However, it says nothing about the non-deterministic nature of the result, failure/empty-result behavior, rate limits, or whether results are cached, which matters for a randomness-based tool.

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?

Front-loaded with the core action and scoping, followed by the return-shape comparison and use cases. Two sentences with little waste, though 'serendipitous discovery across the entire encyclopedia' and the icebreakers/trivia list lean slightly promotional.

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 zero-required-parameter, read-only tool with no output schema, the description does the important work of summarizing the return shape and language behavior. What remains missing is only minor behavioral detail (randomness, error cases), so it is nearly complete for its complexity.

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 `lang` parameter already documents itself with an enum and default. The description only adds 'supports other languages via `lang`,' which is marginal over the schema. Baseline 3 applies when the schema does the heavy lifting.

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 (fetch) and resource (a random Wikipedia article summary) and explicitly contrasts itself with sibling `summary` by noting it returns the same title + summary + thumbnail shape 'but for a surprise topic.' An agent can distinguish this from `summary`, `featured_article`, and `did_you_know` 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?

Gives clear usage context: 'exploration, icebreakers, trivia, and content inspiration when there's no specific subject in mind,' and implicitly routes to `summary` by referencing it as the same-shaped-but-targeted alternative. The condition for choosing this tool is stated, but the inverse case ('use summary when you do have a subject') is only implied rather than spelled out.

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