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

No annotations are provided, so the description carries the transparency burden. It does disclose cost and authentication ('1 Credits', 'no API key', x402/MPP payment), which is useful behavioral context. However, it says nothing about side effects, rate limits, or what data the call actually returns.

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 only two sentences and wastes few words, but the opening 'Search Group: Explore' is vague filler that doesn't clarify behavior. It is concise but front-loads billing rather than function, so it doesn't earn a 4.

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 description omits what the search actually returns (no result format, no domain, no side effects). The schema parameters hint at Twitter-like search behavior, but the description does not explain behavior beyond billing. With no output schema, this is a meaningful gap.

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 input schema already describes all four parameters with titles and descriptions, including the enum for search type and advanced query syntax. The description text adds no additional parameter meaning, so it can at most earn the schema-covered baseline of 3.

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 does not state what the tool actually does beyond 'Search Group: Explore', which essentially restates the tool's name without explaining the resource or behavior being searched. A reader cannot tell from the description alone whether this searches users, posts, media, or something else.

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 or how it differs from sibling tools. The billing note explains payment but not usage context, so the description provides no direction for tool selection.

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