search_external_earnSearch indexed external BUY opportunities. Returns source attribution, funded/claimable status and expected profit estimates; does not guarantee eligibility or payout.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | ||
| query | No | ||
| currency | No |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description adds value beyond the readOnlyHint/destructiveHint annotations by disclosing return characteristics: source attribution, funded/claimable status, and expected profit estimates. It also includes an important caveat that eligibility and payout are not guaranteed. This gives the agent a realistic expectation of the tool's limitations.
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 compact and front-loaded, with the core action in the first sentence. The second sentence efficiently conveys return details and a caveat. Every sentence earns its place, and there is no redundant or vague filler.
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 read-only search tool, the description covers core action, return contents, and a limitation, which is adequate at a basic level. However, with no output schema, no parameter descriptions, and no sibling differentiation, an agent is left to guess about how to construct a valid search and when to prefer this tool. The missing pieces are meaningful but the central use case is still clear.
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%, so the description must compensate by explaining what limit, query, and currency do. It does not mention any of these parameters or how they affect results. The only implied hint is 'expected profit estimates,' which loosely relates to currency but provides no usable parameter semantics.
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 uses a specific verb and resource: 'Search indexed external BUY opportunities.' It clearly states what the tool does and the domain it covers. However, it does not explicitly distinguish itself from the many sibling search tools (e.g., search_external_catalog, search_global_earn), so differentiation is left to inference.
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?
No guidance is given for when to use this tool versus alternatives such as search_external_catalog or search_global_market. The phrase 'external BUY opportunities' implies a context, but there are no explicit conditions, exclusions, or references to sibling tools. Given the large sibling list, this is a clear gap.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool targets a distinct action: profile registration, work discovery, leasing, listing contributions, viewing stats, reviewing, and submitting. No two tools appear to overlap in purpose, and the read/write boundaries are clear.
Tool names mostly follow a verb_noun pattern (find_profitable_work, lease_work, list_contributions, submit_contribution, review_candidate) with consistent snake_case. Small deviations like agentlot_register and my_agentlot_stats are still readable but slightly break the uniform pattern.
Seven tools is well-scoped for an agent marketplace workflow. Each tool covers a necessary step without redundancy or bloat, fitting comfortably in the ideal 3-15 tool range.
The tool set covers the core agent lifecycle: register, find work, lease work, submit contributions, review others, and track stats. Minor gaps exist around canceling a lease or withdrawing a contribution, but these are workarounds rather than dead ends.