GetDDIC_Structure

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. However, the description is only 'Retrieve structure definition' and reveals nothing about side effects, permissions, rate limits, or the nature of the response. There is no indication of whether this is a read-only operation or what the output contains, leaving the agent completely in the dark.

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 extremely concise at only two words, which is efficient but sacrifices necessary detail. It front-loads the key idea but omits any context that would help an agent understand its scope or relationship to sibling tools. It is concise but under-specified.

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?

Given the lack of an output schema and annotations, the description should provide more context about what the tool returns. For a retrieval tool for ABAP DDIC structures, an agent would need to know the structure of the response (e.g., fields, data elements). The description is incomplete and relies heavily on the tool name and param name for inference.

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% for the single parameter 'object_name', described as 'DDIC structure name'. The description adds no additional detail beyond what the schema already provides, so it meets the baseline of 3 for high schema coverage.

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 'Retrieve structure definition' clearly indicates the action (retrieve) and the resource (structure definition). However, it does not differentiate from sibling tools like GetDDIC_Table or GetDDIC_CDS, which also retrieve definitions of related DDIC objects. The purpose is clear but lacks specificity to distinguish among the many similar 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?

No usage guidelines are provided. The description does not specify when to use this tool versus alternatives such as GetDDIC_Table or GetDDIC_DataElements, nor does it mention any prerequisites or context for its use. An agent would have no guidance on selecting this tool over siblings.

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