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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds genuinely useful context (returned fields per result type, sort/timeframe filtering, cursor pagination, and a credit cost), but the cost statement contradicts itself — 'at least 10 Nexscope credits' versus '1 credit per request' — which could mislead an agent about spend.

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 first paragraph is well front-loaded and informative, but the tail is pasted marketing boilerplate ('Reddit Subreddit Search API View Pricing ... 1 credit per request') that restates the purpose and introduces a pricing figure conflicting with the earlier credit statement.

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 usefully enumerates the returned post, comment, and media fields, and covers pagination and cost. Minor gaps remain: it does not say what happens if 'query' is omitted (only 'subreddit' is required) or what the result envelope looks like.

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%, including the enum notes about which sort values apply to comments versus posts, so the schema carries the parameter meaning. The description only glosses 'sort, timeframe filtering, and cursor-based pagination' and adds no syntax or defaults beyond the schema.

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 opening sentence gives a specific verb, resource, and scope: 'Searches within a specific subreddit for posts, comments, and media matching a query.' An agent can distinguish it from subreddit-info siblings, though it never names the site-wide social_reddit_search or social_reddit_subreddit as alternatives, which leaves the boundary implicit.

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 by the phrase 'within a specific subreddit' — an agent can infer this is for scoped Reddit queries, but the description offers no explicit when-to-use versus when-to-use-the-alternative guidance and no prerequisites beyond what the schema states.

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