Check ABAP Cloud readiness

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

With annotations already declaring readOnlyHint=idempotentHint=true, the description adds significant behavioral context: it parses twice at different baseline versions, diffs the results, and separates existing broken code from migration blockers. It explicitly discloses limitations (static, parser-level, no API release checks, no SAP connection, 'ready' is not a certification), going well beyond annotation-provided safety hints.

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 dense but every sentence carries information: method, output categories, grade, use cases, limitations, and an example. It is front-loaded with the core purpose and methodology, then expands with usage guidance and exclusions. No filler words or redundant restatements of the tool name.

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 (dual-pass parsing, diffing, categories, score, grade, verdict) and the presence of an output schema, the description is remarkably complete. It covers what, when, how, and limitations, plus includes an example. All essential decision-making information is present, and the output schema covers exact return structure.

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?

The schema has 100% description coverage for both parameters, so the baseline is 3. The description adds meaning by explaining how baselineVersion functions ('used to separate broken-anyway code from cloud blockers') and provides a concrete example call showing parameter usage. It also enriches the files parameter by implying the source text and optional filename semantics, though the schema already covers this well.

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 opens with a specific verb 'Assess' and clearly defines the resource and goal: 'how far ABAP source is from ABAP Cloud (Clean Core tier 1)'. It also distinguishes itself from sibling tools by detailing its parser-level, static approach and explicitly separating cloud blockers from broken code.

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 explicit use cases: 'when someone asks is this code cloud-ready... before porting classic ABAP into an ABAP Cloud environment, or for a graded tech-debt assessment of an abapGit export.' It also names an alternative (check_released_api) and explicitly states what the tool does NOT do (released-API checks, SAP connectivity, certification), clarifying 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.