Get ABAP Object by URI

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

Description adds that the operation reads 'active' source and that startLine is zero-based. Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the behavioral safety is clear. Description supplements with useful operational context.

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?

Two sentences with no superfluous words. Core purpose and one key parameter detail are front-loaded. Efficient communication.

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?

No output schema and description does not explain the return format (expected source lines) or how lineCount and startLine affect results. With 4 parameters and no schema descriptions, more context is needed for a complete understanding.

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 has 0% description coverage, and the description only clarifies one parameter (startLine zero-based). It does not explain uri, lineCount, or connectionId semantics, leaving significant gaps for correct usage.

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?

Description clearly states 'Read active ABAP source directly by ADT object or source URI,' using a specific verb and resource. It distinguishes this tool from siblings like search_abap_objects by focusing on URI-based direct reading.

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?

Implies usage when a URI is available, but provides no explicit guidance on when to use this tool versus alternatives (e.g., search tools, get_abap_object_lines). No exclusions or prerequisites are mentioned.

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