Fetch social data

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

Annotations already convey readOnlyHint=true and destructiveHint=false; the description adds meaningful behavioral context beyond that: allowlist enforcement via path, raw provider JSON output that is 'large and messy', and credit consumption. This gives the agent a strong sense of cost and output quality before invocation. No annotation contradiction.

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 front-loaded with the core escape-hatch concept and example, then logically flows into platform list, parameter conventions, and warnings. The platform list is long but necessary for a generic tool. Every sentence carries useful information, though the density is slightly high and could be tightened.

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 generic fallback tool with no output schema, the description covers the key operational facts: allowed platforms, parameter naming patterns, allowlist restriction, raw/voluminous output, and credit cost. A minor gap is lack of explicit mention of authentication or rate limits, but annotations and the given details are sufficient for correct invocation.

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%, but the description adds semantic depth beyond the schema: it explains that param names vary per endpoint ('profiles use handle, keyword searches use query, Reddit uses subreddit') and clarifies that path must be an exact allowlisted endpoint. This materially improves an agent's ability to construct valid invocations.

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 states a specific role: 'Generic escape hatch for any ALLOWLISTED long-tail social/web endpoint the dedicated search_* tools don't cover.' This is a clear verb+resource+scope and explicitly distinguishes it from the search_* siblings. Concrete examples like '{path:'/v1/instagram/profile', params:{handle:'nike'}}' further anchor what the tool does.

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?

Usage guidance is explicit and actionable: use this only when 'dedicated search_* tools don't cover' an endpoint, and 'prefer the dedicated search_* tools' as the safer alternative. The WARNING about raw JSON and 'Spends credits' also adds cost/risk considerations that help an agent decide when this tool is appropriate.

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