Define a diamond or gemology term

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations to rely on, the description carries the behavioral burden. It discloses match precedence, return contents, and no-match fallback suggestions. It does not explicitly state that the operation is read-only, but the lookup nature makes this implicit.

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 informative and not padded, though it lists return components and the fallback behavior in a somewhat wordy manner. It remains easy to parse and directly relevant.

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?

Since there is no output schema, the description helpfully specifies the return shape (definition, body, sourced claims, related terms) and no-match behavior. It could mention edge cases like empty input, but it is otherwise sufficient for an agent to call the tool correctly.

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 schema already documents the term parameter with examples and case-insensitivity. The description adds meaningful matching semantics (exact, alias, prefix/word match), which clarifies how the parameter value will be interpreted.

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 action ('look up a single diamond or gemology term'), the resource ('encyclopedia of 90 fact-checked and sourced entries'), and the scope. The matching behavior further distinguishes this tool from broader search tools.

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 implies use for defining a specific term but does not explicitly compare with sibling tools like search_encyclopedia or state when to prefer this tool over alternatives. The guidance is inferred rather than stated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.