Describe how to add an operator/experience to 1001locals: required and optional fields, allowed categories, the free-100-then-5% offer, and the moderation flow. Call this before submit_experience.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries full behavioral burden. It discloses the tool's informational scope (fields, categories, offer, moderation flow) and its role as a prerequisite. It doesn't explicitly state read-only/no side effects, but the name and 'call before submit_experience' imply a safe retrieval.
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 two sentences: the first front-loads purpose and content, the second gives a clear usage instruction. Every clause adds value with no redundancy.
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 zero-parameter tool with no output schema, the description is complete: it tells what information is delivered, covers the important aspects, and specifies when to call it. The sibling context is handled with the explicit ordering.
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?
The tool has zero parameters, so the baseline is 4. The description adds no parameter-specific details because there are none, but it explains the content the tool provides, which is sufficient.
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 clearly states what the tool does: it describes how to add an operator/experience to 1001locals, including required/optional fields, allowed categories, the free-100-then-5% offer, and the moderation flow. It distinguishes itself from siblings by explicitly naming submit_experience as the subsequent action.
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?
Provides an explicit usage directive: 'Call this before submit_experience.' This clearly establishes when to use the tool relative to its sibling, making the workflow unambiguous.
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 clearly distinct purpose: get_experience is by ID, search_experiences is a query, list_* tools enumerate reference data, get_offer explains pricing, and submit_experience is the write operation. No tools overlap in their core responsibilities.
All tool names follow a consistent verb_noun pattern using lowercase and underscores: get_experience, get_offer, list_categories, search_experiences, submit_experience. There are no mixed conventions or vague verbs like 'process' or 'do'.
Eight tools is well within the ideal 3-15 range for a catalog server. Each tool is necessary for the core workflows: browsing reference data, searching, retrieving details, understanding submission requirements, and submitting.
The tool set covers the full lifecycle from discovery (search, get, list) to creation (submit) with supporting schema and pricing information. Minor gaps exist, such as no update/delete operation for experiences and no explicit 'get all' listing, but these are not critical given the submission goes through moderation.