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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered without the description. The description adds semantic context about what Reddit data is for (AI citation surfaces, mention/sentiment/threads), which is useful, but discloses nothing about pagination behavior, ordering, or the cost of large page_size/days values.

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 a one-line purpose, then a bulleted view list and a compact Args block — structure matches how an agent scans. The opening paragraph about Reddit as an AI citation source is mild framing rather than operational instruction, so it is slightly longer than strictly necessary, but no sentence is confusing or wasted.

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 an 8-parameter, no-output-schema read tool, the description supplies what is missing from structured fields: per-view return content (weekly stats, comment tree, sentiment trend), conditional parameter rules, and filter applicability. Safety is covered by annotations. Only return-size/pagination expectations are unstated, so it is nearly complete.

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 only 13% (just user_intent), so the description must carry the load, and it largely does: it documents brand_id, view, thread_id (with the conditional 'Required for view=thread'), status values, which views accept subreddit, and the days/page_size defaults. It even adds a format rule not in the schema ('no r/ prefix' for subreddit). It falls short of 5 only because numeric bounds are left to 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 description names a specific verb (Read) and resource (Reddit monitoring data for the brand) and enumerates the seven views, so an agent knows exactly what slice of data comes back. It does not, however, explicitly distinguish itself from read-only siblings like get_opportunities or write-path siblings like manage_reddit_opportunity and scan_reddit, leaving that inference to the reader.

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?

Each view carries its own usage context: 'opportunities' is for threads the brand hasn't appeared in, 'thread' requires thread_id, 'feed' is chronological mentions. That is clear when-to-use guidance. It stops short of 5 because it never states when not to use this tool or which sibling to prefer for adjacent needs (e.g., managing vs reading Reddit records).

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