CreateClass

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

No annotations are provided, so the description carries full burden. It states 'Creates the class object in initial state' but does not disclose that the class is created in an inactive state, that activation is typically required, or what permissions are needed.

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 brief but contains redundancy ('Operation: Create. Subject: Class.' could be merged). It is front-loaded with the key action, but the repetitive phrasing detracts slightly from conciseness.

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 tool's complexity (8 parameters, no output schema, no annotations), the description is insufficient. It fails to explain the creation workflow (e.g., initial state, need for activation) or what the tool returns. Sibling tools like ActivateClass hint at missing context.

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 coverage is 100% with adequate parameter descriptions (e.g., 'Class name (e.g., ZCL_TEST_CLASS_001)'). The description adds no extra meaning beyond the schema, earning a baseline score of 3.

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 identifies the tool as creating a class ('Create a new ABAP class in SAP system') and distinguishes it from sibling Create* tools. However, it is somewhat redundant with phrases like 'Operation: Create. Subject: Class.'

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 on when to use this tool versus alternatives (e.g., using CreateInterface for interfaces). No mention of prerequisites like requiring a package or transport request, nor when not to use it.

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