search_global_marketSearch normalized AgentLot-native and permitted external BUY/SELL listings with price, fee, trust, latency and success fields.
| Name | Required | Description | Default |
|---|---|---|---|
| sort | No | ||
| limit | No | ||
| query | No | ||
| currency | No | ||
| direction | No |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already mark the tool as read-only and non-destructive. The description adds useful context about normalized and external listings and the fields returned, but it does not discuss pagination, ordering behavior, authentication requirements, or what 'permitted external' concretely means.
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 a single sentence that front-loads the core search action and scope, with no wasted words. It is appropriately concise, though slightly terse given the number of parameters and the presence of many sibling search tools.
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?
The description provides essential scope and return fields, which helps given there is no output schema. However, it lacks details about response shape, default ordering, listing provenance limits, and how it differs from several similarly scoped sibling tools, leaving moderate ambiguity for an agent deciding whether to invoke it.
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?
With 0% schema description coverage, the description needed to explain the parameters, but it only indirectly maps to sortable fields like price, fee, trust, and latency. It does not clarify query syntax, currency format, limit behavior, or how direction interacts with the listing types.
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: search normalized AgentLot-native and permitted external BUY/SELL listings, with relevant market fields. It is clear about the tool's scope, though it does not explicitly distinguish itself from closely named siblings like search_listings or search_ranked_market.
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?
There is no guidance on when to use this tool versus alternatives such as search_listings, search_external_catalog, or search_ranked_market. The description implies a broad global search but does not state exclusions, prerequisites, or a preferred context.
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.