check_post_visibility

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

The description adds useful behavioral context beyond the readOnlyHint by explaining that visibility is checked against the /new listing, not just profile existence. It does not disclose the meaning of scan_depth, possible listing lag, or other operational caveats, but it does communicate the core detection 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?

The description is a single, well-structured sentence that front-loads the core purpose and defines the key terminology. Every word contributes meaning, with no filler or redundancy.

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?

The output schema and readOnly annotation reduce some burden, but significant context is still missing: scan_depth semantics, account behavior, and operational expectations around timing or listing state. Knowing only that post_id is required is insufficient for confident invocation of a tool with three parameters.

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 0%, and the description only implicitly clarifies post_id. The account and scan_depth parameters are entirely unexplained, so the agent cannot understand the impact of scan_depth or when account is needed. The description does not compensate for the missing parameter documentation.

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 states a specific verb ('Detect') and resource ('post visibility in its subreddit's /new listing vs profile'), making the tool's purpose immediately clear. It also distinguishes this from account-level checks like check_shadowban by focusing on a single post's visibility.

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 use case is implied clearly: use this when you need to detect silent removals or determine whether a post is actually visible in the subreddit listing. However, there is no explicit guidance on when not to use it or which sibling tool to prefer, leaving the agent to infer the boundary against alternatives.

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