get_sub_by_name_info

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

The readOnlyHint annotation already conveys the safety profile, and the description adds no behavioral traits beyond the returned content. It does not contradict the annotation, but also does not disclose any additional side effects, limits, or output characteristics.

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 four words and front-loads the three key content types with no filler. It is highly concise, though converting it to an explicit sentence would slightly improve structure.

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 read-only one-parameter tool with no output schema, the description adequately outlines what the call returns (metadata, rules, moderators). It is sufficient for an agent to decide to invoke it, though it leaves the exact metadata fields unspecified.

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 only parameter, name, is fully described in the schema with a useful 'no r/ prefix' instruction (100% coverage), so the description does not need to add parameter details. It simply reinforces the subreddit context without adding new semantic value.

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 identifies the resource (subreddit) and the content categories (metadata, rules, moderators), which distinguishes it from siblings like get_sub_by_name_top that return posts. It is clear but uses a noun phrase rather than an explicit verb.

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 intended use is implied by the listed data categories—an agent would select this when it needs subreddit overviews—but there is no explicit statement of when to prefer this tool over get_sub_by_name_top or other siblings, and no when-not-to-use guidance.

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