Manage RAP Generator

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

The description adds information about confirmation keys for generate, publish, and unpublish, which hints at side effects. However, given the destructiveHint:true annotation, more detail about what gets destroyed and other behavioral traits is expected. The description does not contradict annotations.

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 short, but the second sentence is cryptic and poorly structured. It could be improved with bullet points or clearer separation of information. However, it is not excessively verbose.

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 complex tool with 14 parameters, multiple actions, a nested content object, and no output schema, the description is critically incomplete. An AI agent cannot determine which parameters are needed for each action, how to use the nested objects, or what to expect as a response.

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?

With 0% schema description coverage and 14 parameters, the description is expected to compensate but fails entirely. It only mentions the action enum values (already in schema) and confirmation strings, adding no meaning to the many other parameters like content, transport, or generatorId.

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 enumerates a clear set of actions (availability, get_schema, get_defaults, validate, preview, generate, publish, unpublish, service_details) and identifies the resource as RAP generator. It distinguishes the tool from its ABAP-focused siblings by its specific domain.

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 lacks explicit guidance on when to use the tool versus alternatives, and does not explain the sequencing or prerequisites for the listed actions. The cryptic confirmation strings provide some context but no clear usage instructions.

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