lookup_glossary

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

No annotations are provided, so the description is the only source. It implies a read-only lookup operation and indicates that the output includes a definition and explanation, but it does not explicitly state side-effect-free behavior, error handling, or access requirements. For a simple lookup, this is minimally adequate.

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 clear sentence that efficiently conveys purpose without unnecessary words.

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?

The description sufficiently explains what the tool does for a simple single-parameter lookup. It does not include details on return format or edge cases, but the statement that it returns a definition and explanation is adequate given no output schema and low complexity.

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 fully describes the 'term' parameter with examples. The description does not add additional semantic detail beyond restating that a term is looked up, so it does not elevate above the schema baseline.

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: looking up a term in the ABAP Glossary to retrieve its definition and explanation. The verb 'look up' and specific resource 'ABAP Glossary' differentiate it from sibling tools like search_abap_keyword or browse_main_topics.

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?

There is no guidance on when to use this tool versus the sibling tools. It does not mention alternatives, prerequisites, or specific scenarios, such as when a user needs a formal glossary definition rather than a broader keyword search.

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