lookup_term

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

No annotations, but description discloses case-insensitivity, return type (entry or error dict), and parameter examples. Sufficient for a simple read tool.

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?

Extremely concise: one line for purpose, plus args/returns. No wasted words. Front-loaded with key behavior.

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?

Covers all essentials: exact match, case-insensitivity, single parameter with examples, return type. Minor gaps: no mention of error cases beyond 'error dict', but adequate for a simple lookup.

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?

With 0% schema coverage, description adds concrete examples (e.g., 'usaf', 'USAF', 'US Air Force') and clarifies parameter purpose beyond the schema.

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?

Clearly states 'Exact lookup by term or alias (case-insensitive)', specifying verb, resource, and matching behavior. Distinguishes from sibling 'search_glossary' which likely does fuzzy search.

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?

Implies use for exact matching via 'Exact lookup' but does not explicitly state when not to use or contrast with siblings like search_glossary. No alternatives mentioned.

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