reddit_search_users

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds that it returns username, karma, and account age, which is useful context, but it doesn't disclose additional behavioral traits like pagination limits or rate limits. This is adequate but not rich.

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 two concise sentences plus an example, with no wasted words. The first sentence states what it does, the second explains why and when to use it, and the example provides a quick reference. Perfectly front-loaded.

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 the 4-parameter schema with full descriptions and read-only annotations, the description is complete for a search tool. It covers the tool's scope, return fields, use case, and an example. No output schema exists, so the description's mention of return values is necessary and provided.

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% with detailed docs for all parameters, so the baseline is 3. The description adds a concrete example q='spez' and clarifies 'by name or keyword', which enhances understanding beyond the schema's formal parameter descriptions.

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 'Search' and the specific resource 'Reddit users (redditors)', with scope 'by name or keyword'. It also differentiates from sibling tools by focusing on user search, and provides an example (q='spez') that reinforces the tool's specific purpose.

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 gives clear context: 'Use to find a person's handle before fetching their profile or comments.' This provides an explicit use case and implies when to choose this tool over alternatives. However, it doesn't explicitly mention when not to use it or name alternative tools.

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