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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds the random-selection behavior, but does not explain how randomness works, whether results may repeat, or what a caller should expect beyond a post. This is acceptable for a simple tool but adds limited behavioral detail.

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?

The description is a single front-loaded sentence that communicates the core behavior immediately. The 'surprise pick' clause adds tone and context without unnecessary bulk, so every word earns its place.

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-parameter, read-only tool with full annotation coverage, the description is essentially complete: an agent knows what the tool does and that it is safe to call. It does not specify the output format, but 'Return a random post' gives enough grounding for a no-input utility.

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 has zero parameters and the schema is complete, so there are no parameter semantics to document. The description appropriately needs to say nothing about inputs. A baseline of 4 applies because no parameters exist.

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?

The description states a specific action ('Return') and resource ('random post from the blog'), clearly distinguishing this from siblings like read_post, search_posts, and list_recent. The 'surprise pick' phrasing reinforces the tool's unique random-selection purpose without being tautological.

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 'surprise pick' wording implies use for serendipitous discovery, but the description does not explicitly state when to use this tool versus the many sibling tools. No exclusions or alternative comparisons are provided, so usage guidance is only implied.

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