reddit get saved audiences

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

Annotations already declare read-only, idempotent, non-destructive, so safety needs no restating. The description adds genuinely non-obvious behavior: pagination returns an opaque cursor and each subsequent page requires a separate call (no auto-pagination), which an agent cannot infer from annotations or schema alone.

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?

Two compact sentences with the core purpose front-loaded and behavioral detail following. Minor redundancy with the schema's cursor/next_cursor wording, but nothing is 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?

An output schema covers return values and annotations cover the safety profile, so the description only needs purpose and pagination semantics — both are present. The absence of any account-scoping or sibling-routing note is the only meaningful gap for a list tool with one required parameter.

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%, so limit, cursor, and adAccountId are fully documented in the schema, establishing the baseline of 3. The description's only parameter-adjacent content is the opaque-cursor statement, which the cursor schema field already explains.

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?

States a specific verb and resource ('Read Reddit saved audiences') and names what the payload contains (native configuration, configured/effective status). It is clearly a list-all operation, but it never explicitly contrasts itself with the singular reddit_get_saved_audience sibling, which is the main ambiguity an agent could hit.

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: 'Read ... saved audiences' plus a pagination note tells an agent this is a listing call. There is no explicit statement of when to prefer this over reddit_get_saved_audience or any prerequisite/account-scoping guidance.

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