Read ABAP Type Hierarchy

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is clear. The description adds the 'bounded' aspect but doesn't explain behavioral details like pagination or return structure. With annotations covering core traits, a score of 3 is appropriate.

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, making it extremely concise and front-loaded. However, it is almost too brief, sacrificing valuable information. Still, it earns points for lack of verbosity.

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?

With 7 parameters, no parameter descriptions, and an output schema presumed present, the description is too minimal. It fails to explain key aspects like what 'bounded' means, how results are limited, or how to interpret the output. The tool's complexity demands more completeness.

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 0%, meaning no parameter descriptions exist. The description does not explain any of the seven parameters (e.g., systemId, fileUri, limit, superTypes), leaving the agent with no help beyond the raw schema. This is a critical gap.

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 reads an ABAP type hierarchy with a 'bounded' qualifier, differentiating it from sibling semantic tools like 'sap.semantic.components' or 'sap.semantic.definition'. However, it does not elaborate on what 'bounded' means, slightly reducing clarity.

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 guidance is provided on when to use this tool versus alternatives (e.g., sap.semantic.components or other hierarchy tools). There is no mention of context, prerequisites, or exclusions.

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