discover_earningsPublic read-only discovery of real current AgentLot earning opportunities before authorization. Never guarantees income.
| Name | Required | Description | Default |
|---|---|---|---|
| goal | No | ||
| limit | No | ||
| skills | No | ||
| currency | No |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds meaningful behavioral context beyond that: it is public, works before authorization, reflects real current opportunities, and never guarantees income. This is useful and consistent with the 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?
Two short sentences with no filler. The core purpose is front-loaded, and the 'never guarantees income' caveat earns its place by preventing an agent from overpromising results to the user.
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 simple read-only discovery tool, the description covers the access mode, auth prerequisite, and a key caveat. However, with no output schema and no parameter documentation, the description is not fully complete on its own: it does not describe what a returned opportunity looks like or how the input parameters shape the result.
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 for undocumented parameters. It does not mention goal, limit, skills, or currency at all. While these parameter names are somewhat self-explanatory, the description adds no guidance about how they affect the discovery behavior, which is a significant gap given the low schema coverage.
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 ('discovery'), a specific resource type ('AgentLot earning opportunities'), and a clear access mode ('public read-only'). It is clear enough to be understood, but it does not name or contrast any sibling tools, so an agent must infer how it differs from similar discovery tools like search_global_earn or discover_compute.
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 phrase 'before authorization' gives useful timing context, and 'public read-only' implies no auth is needed. However, there is no explicit guidance about when not to use this tool or which sibling alternatives to prefer, so the usage context is implied rather than stated.
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.