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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description adds valuable context beyond that: it warns that the response is RAW provider JSON (large and messy), that it spends credits, and that non-allowlisted paths are rejected. These are clear behavioral traits not implied by annotations.

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 dense but every sentence carries useful information: purpose, platform list, param naming, raw JSON warning, and credit cost. It could be slightly condensed, but it front-loads the core purpose and alternative routing before the details, so it's 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 this is a generic fallback tool with no output schema, the description covers the essential aspects: what endpoints are allowed, how params vary, the nature of the response, and the credit cost. It doesn't list all exact paths, but provides enough guidance for an agent to reason about allowed usage.

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 coverage is 100%, so the baseline is 3. The description goes further by explaining that param names vary per endpoint and gives examples (handle, query, subreddit), which helps an agent construct valid params that the schema alone (with generic 'params' object) does not convey.

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 that this is a generic escape hatch for allowlisted social/web endpoints not covered by the dedicated search_* tools, with a concrete example. It distinguishes itself from siblings by explicitly referencing the search_* tools and listing supported platform families.

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?

It explicitly says to prefer the dedicated search_* tools and to use this only when they don't cover the endpoint. It also hints at the param naming conventions per platform, giving an agent the decision criteria to select this tool over alternatives.

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