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

No annotations are provided, so the description carries the full burden of behavioral disclosure. The description is nearly empty, lacking any information about side effects, access requirements, rate limits, or pagination behavior. The schema hints at paging via nextPage, but the description does not mention any behavioral traits. It does not even state that it is a read operation, but since the tool name implies fetching comments, it may be read-only; however, without explicit disclosure, it's insufficient.

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 extremely short, but it is under-specification, not conciseness. It contains a single sentence that repeats the name and adds billing info, which is not useful. It does not front-load important information; it is essentially a placeholder. The description is too sparse to be considered well-structured.

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?

Given that the tool has 3 parameters, no output schema, and no annotations, the description is severely incomplete. It lacks any explanation of what the tool returns, how pagination works, or how it relates to similar tools. The complexity is moderate, but the description provides virtually no context. This is far below the minimum viable.

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?

The schema description coverage is 100%, meaning each parameter is documented in the schema with explanations and examples. The description adds no additional semantic meaning beyond the schema. For instance, the description does not clarify that groupId is the subreddit post ID or that sort options are for comment ordering. Since the schema already covers parameter semantics, the baseline is 3, and the description does not enhance it.

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 is merely a repetition of the tool name and title, stating 'subreddit/comments Group: Subreddit. Billing per call: 1 Credits.' It does not state what the tool does, such as retrieving comments from a subreddit. It fails to mention that it fetches comments for a given subreddit post identifier. The verb and resource are not explicit, and it does not distinguish from sibling tools like get_posts_comments or get_search_comments. Therefore, it is a tautology.

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 no guidance on when to use this tool versus alternatives. It only indicates billing cost, which is irrelevant for selecting the tool. There is no mention of context, prerequisites, or exclusions. The tool name suggests it is for subreddit comments, but the description doesn't clarify when to choose it over siblings like get_posts_comments or get_search_comments.

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