lookup_element_definition

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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds value by clarifying the operation is 'read-only or local', scoping the search to specific dictionaries, and noting it is an alias. It does not contradict annotations and adds context beyond the structured safety hints.

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 sentences, front-loaded with the primary purpose, followed by a behavioral note. No filler or redundant information; every clause contributes to understanding the tool.

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 lookup tool with 2 optional parameters, full schema coverage, and safety annotations, the description provides sufficient context about scope and behavior. It does not explain return values, but no output schema exists, and the tool is straightforward enough that this is not a major gap.

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 description coverage is 100%, and the description echoes the schema's parameter descriptions but does not add substantial new meaning. The alias relationship between 'element' and 'query' is mentioned, but it is already present in the schema. Baseline 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?

The description clearly states the tool is an alias for lookup_x12, used to search segment maps and ack codes within specific EDI dictionaries (850/810/856/837). This provides a specific verb ('search') and resource ('segment maps and ack codes'), distinguishing it from siblings like parse_edi or validate_edi.

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 lookups and notes it is read-only or local, but it does not explicitly state when to use this tool versus lookup_x12 or other siblings. No exclusions or alternative conditions are given, so usage context is only implied.

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