list_languagesReturns all languages with their IDs. Use these IDs in search_brokers (languageIds) to find brokers who speak specific languages. Call this when you need to discover which language IDs to use.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and destructiveHint=false, covering the safety profile. The description adds that it returns 'all' languages, implying a complete list without pagination, but it does not describe the response format or any additional behavioral nuances. This is similar to the get_calls calibration example: it adds some context but lacks rich behavioral detail.
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 three sentences, each earning its place: it states the output, gives a concrete usage example with a sibling tool, and specifies when to call it. There is zero wasted verbosity, and the structure is logical.
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 the tool's simplicity (no parameters, no output schema), the description is complete. It answers what the tool does, what is returned (languages with IDs), and how to use the result. It also integrates with the sibling tool landscape, making it fully actionable for an agent.
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 schema is fully self-explanatory (100% coverage). The description doesn't need to add parameter details. Per the rubric, a baseline of 4 is appropriate for a zero-parameter tool, and the description provides no conflicting or redundant information.
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's function: 'Returns all languages with their IDs.' It identifies the resource (languages) and the output (IDs), and distinguishes itself from sibling tools by its focus on language reference data, not brokers or businesses.
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 description provides explicit usage guidance: 'Use these IDs in search_brokers (languageIds) to find brokers who speak specific languages' and 'Call this when you need to discover which language IDs to use.' It tells the agent when and how to invoke the tool, which is exactly what the dimension asks for.
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 resource and action: search vs. get vs. contact for brokers and businesses, list operations for categories and languages, and an auth check. There is no meaningful overlap between tools.
All tools use snake_case with a clear verb_noun structure (contact_, get_, list_, search_), and who_am_i is a conventional exception. The pattern is consistent and predictable.
Nine tools is well-scoped for a business-listing marketplace. Each tool serves a clear purpose in the discovery and contact workflow without redundancy or bloat.
The tool set covers the full user journey: searching and viewing businesses and brokers, retrieving supporting content (categories, languages), contacting parties, and verifying authentication. No critical operations are missing for the apparent domain.