Get RAP Defaults

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior, so the safety profile is covered. However, the description adds minimal behavioral context—only that it works 'through the shared RAP generator capability.' It doesn't disclose pagination with offset/length, possible variations based on generatorId, or what 'defaults' means operationally, so the added value is low.

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, short sentence and is front-loaded with the main action. It's concise with no fluff, but the extreme brevity borders on under-specification. Still, for what it contains, the structure is efficient and clear, earning a 4 rather than a 5 because it omits essential value-add information.

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?

Despite having a complex schema with 7 parameters (4 required) and an output schema, the description provides almost no context. It fails to explain the purpose of the tool in any depth, the meaning of the parameters, or the nature of the return value. The completeness is severely lacking, making the tool nearly unusable without external knowledge.

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 schema description coverage at 0%, the description must compensate by explaining the parameters, but it does not. Parameter names like referenceObjectName and generatorId are left to guesswork, and the enum values for generatorId are undocumented. The description fails entirely to clarify any of the 7 input parameters, leaving the agent blind.

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 ('Get') and resource ('RAP Defaults'), clearly indicating a retrieval operation. However, it doesn't differentiate from sibling tools like sap.rap.schema or sap.rap.generate, so while the core purpose is clear, the exact domain of 'defaults' remains ambiguous.

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 provides no guidance on when to use this tool versus alternatives. It doesn't mention typical use cases, prerequisites, or why one would choose this over sap.rap.generate, sap.rap.schema, or sap.rap.preview. The phrase 'through the shared RAP generator capability' hints at a context but doesn't explain when to invoke it.

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