list_gem_termsList the gemmological terms available in The Gem Lexicon, optionally filtered to one subject section. Use this to discover what can be defined before calling define_gem_term.
| Name | Required | Description | Default |
|---|---|---|---|
| section | No | Optional section filter, e.g. "Treatments & Enhancement". |
| Name | Required | Description | Default |
|---|---|---|---|
| terms | Yes | ||
| sections | Yes | All lexicon section names. | |
| term_count | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already cover read-only, idempotent, and non-destructive behavior. The description adds the useful detail that listed terms are valid targets for definition, but it does not disclose additional behavioral context such as pagination or availability limits. Output schema softens that gap.
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 compact sentences deliver the core behavior, scope, and sibling relationship with no unnecessary detail. The most important usage guidance is placed at the end of the second sentence and remains effective.
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?
This is a simple listing tool with one optional parameter, a complete schema, an output schema, and strong annotations. The description gives enough context for an agent to invoke it appropriately without missing information.
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 coverage is 100% and the section parameter already has a clear description and example. The tool description does not add meaning beyond the schema, so the schema-heavy baseline of 3 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?
Description states a specific action (list), a specific resource (gemmological terms in The Gem Lexicon), and a scoping option (filter by subject section). It also positions the tool as a discovery precursor to define_gem_term, helping distinguish it from the nearest sibling.
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?
It explicitly tells an agent to use this tool to discover what can be defined before calling define_gem_term, providing a clear when-to-use. However, it does not mention search_gem_knowledge or explain when to choose that sibling instead, leaving a small gap.
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 has a clearly distinct role: enumerating the lexicon, looking up an exact definition, and full-text searching the broader reference library. An agent can easily choose the right tool based on whether it needs a list, a definition, or a broad search.
All tool names follow the same snake_case verb_noun convention: define_gem_term, list_gem_terms, search_gem_knowledge. The pattern is consistent and makes the toolset predictable.
Three tools is a well-scoped size for a read-only reference server. Each tool has a distinct purpose and none feels redundant or extraneous.
The core workflow of list, define, and search is well covered for a gemmology reference library. The only minor gap is that the 25 buyer's handbooks can be searched but not independently listed or retrieved beyond search snippets.