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

Annotations already cover the read-only, open-world nature, and the description adds real behavioral context beyond them: a per-call price of $0.002 USDC via x402 on specific chains, and the fact that failed calls are not charged. It also discloses the ~25-item cap and hidden-data limits, though it says nothing about latency, rate limits, or account/auth prerequisites for the payment flow.

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 tight paragraph, front-loaded with the payload contents, then the scope limits, then the price. No filler sentences; every clause carries information an agent would act on.

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?

An output schema exists, yet the description still summarizes the return shape, and it covers the two things an agent cannot infer from structured fields — data completeness (no karma/account age, ~25 posts) and cost/charging behavior. Nothing needed to call it correctly is missing.

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 coverage is 100% and the single username parameter is already documented in the schema (no u/ prefix, 3-20 letters/digits/_/-). The description adds no syntax or formatting detail beyond that, so the baseline of 3 applies.

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 names the resource precisely (Reddit user profile from the public user feed) and enumerates exactly what is returned: name, subtitle, and ~25 latest submitted posts with title, subreddit, date, and link. It is unambiguous what the tool produces, though it never names the sibling social_reddit_posts or explicitly contrasts the two.

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 implied through negative scoping — 'No karma, account age or hidden profile data; the feed does not show them' tells the agent not to call this when those fields are needed. However, there is no explicit 'use this when...' statement and no named alternative for post-level or comment-level queries.

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