Activate ABAP Source

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

Annotations already mark it as idempotent, non-destructive, and not read-only. The description adds the constraint of same-system and the limit of 100 resources, but does not disclose further behavioral traits like activation consequences or error handling.

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 clear sentence, front-loaded with the key action and constraints. However, it is perhaps too terse and could benefit from a sentence about parameter semantics or usage.

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 has an output schema and two parameters with 0% schema coverage, the description fails to explain activation context, prerequisites, or distinguish among many sibling tools. Significant gaps remain for an agent to use this tool properly.

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 0%, so parameters are undocumented. The description partially explains 'resourceUris' by stating 'one or up to 100 ABAP Resources', but leaves 'systemId' completely unexplained. No added detail beyond the schema's structural constraints.

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 verb 'Activate' and the resource 'ABAP Resources' with constraints: 'one or up to 100' and 'same-system'. This distinguishes it from siblings like sap.source.diagnose or sap.source.read_batch, which have different purposes.

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, nor any context about prerequisites or when not to use it. The description only states what it does, not when it should be chosen over other tools like sap.source.patch or sap.execution.execute.

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