advice_random

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

Annotations already declare readOnlyHint, destructiveHint=false, openWorldHint, and idempotentHint, so the safety profile is fully covered by structured data. The description adds nothing beyond that (no note that results vary per call, no indication of data source), which is acceptable but thin. Worth noting: idempotentHint=true sits oddly with a "random" tool whose output changes per invocation, though that is an annotation issue rather than a description contradiction.

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?

A single short sentence with the verb and resource front-loaded and zero filler. Nothing could be removed without losing meaning.

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 trivial no-parameter fetch, annotations carry the operational profile, so little is required. However, there is no output schema, so the description is the only place to indicate what the response looks like (a plain advice string), and it does not say.

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?

The tool takes zero parameters, so the baseline of 4 applies; there is nothing for the description to document in this dimension.

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 ("Get a random piece of advice") that an agent can act on without opening the schema. It does not, however, explicitly differentiate itself from the sibling advice_search and advice_by_id tools, leaving the agent to infer that "random" is the distinguishing behavior.

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?

Usage is only implied: "random" suggests use when you want a non-targeted pick, versus advice_search or advice_by_id for targeted retrieval. There is no explicit when-to-use or when-not-to-use statement, though for a zero-parameter novelty tool the inference is fairly safe.

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