get_my_saved

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

Annotations only mark readOnlyHint/openWorldHint; the description adds critical details: required user credentials (REDDIT_USERNAME/REDDIT_PASSWORD), pagination behavior ('Returns up to limit items plus an after cursor'), and privacy context ('saved items are private'). This goes far beyond the annotations and fully discloses the tool's behavior.

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?

Every sentence earns its place: purpose, credential requirement, pagination output, and a clear distinction from a sibling tool with an explicit cross-usage warning. No redundant phrasing or filler.

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 a two-parameter read-only tool with no output schema, the description covers purpose, auth, pagination, alternative tools, and edge-case privacy constraints. It answers all likely agent questions and leaves nothing structurally ambiguous.

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 the schema fully documents each parameter. The description mentions `limit` and `after` in a pagination context, reinforcing their purpose, but doesn't add new syntax or formatting details beyond what the schema already provides—baseline 3 is appropriate.

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?

Description explicitly states 'Get the authenticated user's saved posts and comments (private to the account)', naming the resource and scope. It distinguishes from siblings by pointing to 'get_my_overview' for authored activity and clearly stating the lack of cross-user access, eliminating ambiguity.

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 description provides explicit when-to-use ('Get the authenticated user's saved posts/comments'), an alternative ('Use get_my_overview for your authored activity'), and when-not-to-use ('Do NOT use this for another user'). It even covers the auth prerequisite, offering complete guidance.

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