RuntimeRunClassWithProfiling

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

No annotations are provided, so the description must fully disclose behavior. It states that the tool executes a class with profiling and returns IDs, but it does not mention side effects (e.g., system load, resource consumption), authorization requirements, or whether the class is executed in the current session. This is insufficient for an execution tool.

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, concise sentence that conveys the core purpose without redundancy. It is front-loaded with the key action and result. However, it sacrifices necessary detail for brevity.

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 tool has 15 parameters, no output schema, and no annotations. The description does not explain how to configure profiling options, interpret the return values, or handle errors. This is highly incomplete and insufficient for an agent to use the tool effectively.

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?

There are 15 parameters, but schema description coverage is only 13%. The description provides no information about any parameter, leaving the agent to rely solely on parameter names and the sparse schema descriptions. For example, the boolean flags like 'all_db_events' have no context on their meaning or effect.

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 uses a specific verb 'Execute' with the resource 'ABAP class with profiler enabled' and mentions the return values (profilerId + traceId). This clearly distinguishes it from sibling tools like RuntimeAnalyzeProfilerTrace, which analyze existing traces.

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 usage for profiling a class execution, but it provides no explicit guidance on when to use this vs alternatives, such as when to choose RuntimeCreateProfilerTraceParameters or RuntimeAnalyzeProfilerTrace. No context on prerequisites or exclusions.

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