GTech Networks DB: get glossary term

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

No annotations are provided, so the description carries full burden. It only states that it looks up a term definition but does not disclose any behavioral traits like error handling (e.g., if term not found), authentication requirements, or whether it has side effects. This is minimal for a tool with no annotations.

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 a single sentence with a database-specific preamble, front-loading the restriction. No unnecessary words; every part earns its place.

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?

For a simple one-parameter lookup tool, the description covers the purpose and parameter meaning. However, it does not specify the return format (e.g., definition as string, object with fields) or behavior for missing terms. Given no output schema and no annotations, it is minimally adequate but has gaps.

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 gives no description for the 'term' parameter, but the tool description adds meaning by specifying it is a GTech/NetWorks Core domain term and provides examples (e.g., Feature, Component, Legend). This helps the agent understand what kind of string to provide.

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 looks up a glossary term's definition in a specific database (GTech/Hexagon). It provides examples of terms (Feature, Component, Legend), making the purpose precise and differentiating it from sibling tools that deal with contexts, relationships, or schemas.

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 indicates the tool is for looking up definitions of domain terms in a specific database, implying use cases where such definitions are needed. It does not explicitly state when not to use it or mention alternatives, but the sibling context suggests it's specialized for this purpose.

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