The connected Reddit account’s own posts

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

The description discloses the exact fields returned (id, title, subreddit, score, comment count, removed status, editability), which is behavioral detail beyond the annotations. It also explains the purpose and why the tool exists. It explicitly states 'Read-only, 0 credits' which aligns with readOnlyHint=true and destructiveHint=false. No contradiction with annotations.

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 description is moderately long but each sentence carries value. It is front-loaded with the core purpose and a bolded callout for the critical postId source. The structure flows from purpose to usage note to requirements. It is not overly verbose, though it could be slightly tightened.

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 simple list tool with 0 required parameters and no output schema, the description is thorough. It covers purpose, usage context, prerequisites, and the content of returned data. There is no missing information an agent would need to call it correctly; even the reason for the tool's existence is explained.

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% — all three parameters (sort, limit, cursor) have descriptions in the schema. The description does not add extra semantic meaning beyond what the schema provides. It mentions the default for sort but that is also in the schema. Thus, 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?

The description clearly states the verb 'list' and the resource 'the connected Reddit account’s OWN submissions', listing the specific fields returned. It distinguishes itself from other Reddit tools by emphasizing that it returns the account's own posts and explicitly notes it is the source of postId for every other Reddit tool. This differentiates it from search_reddit and other listing tools.

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 usage guidance: it tells the agent that postId comes from this tool, and contrasts with post_to_reddit which only gives an id at publish time. It also states prerequisites ('Needs Reddit connected') and clarifies it is read-only with 0 credits, giving clear context on when to invoke it.

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