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

No annotations are provided, so the description carries the full transparency burden but discloses nothing about behavior—no return format, no result semantics, no side effects. The 'Billing per call: 1 Credits' note is the sole behavioral detail, which is thin. The tool's behavior (what does it actually search? users only? posts?) is completely opaque.

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?

At 13 words, the description is certainly short and front-loaded with the identifier. However, the brevity reads as under-specification rather than deliberate concision—there simply isn't substantial content to evaluate for quality.

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?

With 0 required params, no output schema, and no behavioral annotations, the description is the only place for an agent to understand tool limits, return shape, or relationship to get_v1_search/get_v2_feed. It does not clarify what 'search' returns, how it differs from v1, or what 'credits' mean functionally. This is inadequate for an agent to confidently select this tool over its sixteeen siblings.

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% — both 'limit' ('Result limit') and 'username' ('Search query for users') are documented. The description itself adds no parameter meaning, but since schema coverage is high, the baseline score of 3 applies.

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 'v2 / Search' restates the tool name without adding meaning—it's essentially a tautology. The 'Group: v2 / Explore' categorization and billing note add no clarity about what the tool does. Purpose must be inferred from the name and the username parameter, not from the description itself.

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?

There is no guidance on when to use this tool versus alternatives. Notably, the sibling list includes get_v1_search and get_v2_feed, creating obvious ambiguity about version differences, yet the description offers no differentiators or usage context.

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