Return all trades and service categories available in the index (e.g. VVS-installatør, Elektriker). Call this first if you are unsure which trade term to use when searching.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true; description adds context about the returned data (list of trades and categories). No contradictions. Adequate behavioral disclosure for a read-only tool with no destructive potential.
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 concise sentences with no waste. Front-loaded with action and examples, earning its length.
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?
Given no parameters, no output schema, and adequate annotations, the description fully informs an agent about what the tool does and when to use 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?
No parameters exist, schema coverage is 100%, so description does not need to add param info. Baseline of 4 is appropriate.
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 the tool returns all trades and service categories, with concrete examples. It distinguishes from siblings by indicating when to use this tool (uncertainty about trade term).
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?
Explicitly says 'Call this first if you are unsure which trade term to use when searching', providing clear usage context. It does not explicitly mention alternatives or when not to use, but sibling tools are listed.
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 performs a distinct function: finding providers by criteria, fetching details by ID, and listing available trades. No overlap or ambiguity.
All tool names follow a consistent verb_noun pattern in camelCase, making the purpose clear and predictable.
Three tools are perfectly scoped for a service provider index, covering search, detail retrieval, and trade listing without bloat or deficiency.
The tool set provides complete coverage for the domain: discovering available trades, searching for providers, and retrieving full details. No obvious gaps.