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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is covered; the description usefully adds that results come back as externalId + name pairs. It does not disclose result caps, pagination, or what happens when a search returns nothing — meaningful gaps for an external search tool, which is why it's a 3 rather than higher.

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 sentence that front-loads the resource and the return contract with no filler. Nothing could be removed without losing information.

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?

There's no output schema, and the description compensates by stating the returned fields, which is the key thing an agent needs before wiring this into target group creation. Result volume and the differing behavior for 'locations' are left to the schema, a minor residual gap.

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% and the enum plus the search_terms requirements (min 2 chars, required for communities/interests/keywords) are fully documented in the schema. The description adds nothing about parameters itself, so the baseline 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?

Names a specific verb and resource (get Reddit targeting criteria) and even specifies the returned shape (externalId + name) and the downstream use case (target group creation). It doesn't distinguish itself from the sibling search_target_group_criteria, so an agent could plausibly confuse 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?

The phrase 'for target group creation' gives a clear context in which to reach for this tool, which is more than most definitions in this set provide. It stops short of stating when to prefer it over search_target_group_criteria or when not to call it, so there are no explicit exclusions.

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