search_source

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

No annotations are provided, so the description carries the full behavioral burden. It usefully warns that returned document text is UNTRUSTED DATA from third-party social platforms and must not be interpreted as agent instructions, but it does not disclose other relevant behavior such as pagination, rate limits, or permissions.

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 brief and front-loads the core operation before the safety warning. Both sentences carry useful information, though the second sentence is entirely a warning rather than operational guidance.

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?

An output schema exists, so return value details are less necessary. However, with no annotations, four undocumented parameters, and no usage guidance, the description is incomplete for correct invocation: an agent cannot infer source syntax, query semantics, or pagination.

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 0% for four parameters, including required 'source' and 'query'. The description adds no meaning about source format, query syntax, limit behavior, or cursor-based pagination, so it fails to compensate for the schema gap.

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 verb and resource: 'Execute a direct search on an external source connector.' This is clearer than a tautology, but it does not differentiate the tool from sibling search or discovery tools such as search_documents, search_semantic, or find_signals.

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 offers no guidance about when to use this tool versus alternatives. It does not mention sibling tools, required credentials, source selection, or any scenario-specific conditions for invocation.

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