Get ABAP Object Workspace URI

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

Annotations already declare readOnlyHint=true and idempotentHint=true, indicating safe, idempotent behavior. The description adds value by specifying the output is a 'stable' URI, reinforcing idempotency and the intended use for editing, without contradicting 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 a single sentence front-loaded with the core verb 'Resolve'. Every word serves a purpose, and there is no extraneous 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?

The tool has three required parameters and no output schema. The description fails to explain parameter details or return value. Given the moderate complexity and lack of schema descriptions, the description is incomplete.

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 for all three required parameters (objectName, objectType, connectionId), the description provides no information about them. It only mentions 'exact ABAP object', which is insufficient to guide parameter values.

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 specifies the verb 'Resolve', the resource 'ABAP object to a stable adt:// URI', and the use case 'headless source-edit tools'. This clearly distinguishes it from siblings like get_abap_object_url, which may return a different URI format.

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 states the tool is 'usable by headless source-edit tools', providing clear context for when to use it. However, it does not explicitly mention when not to use it or list alternatives like get_abap_object_url, so it misses explicit exclusions.

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