GetProgram

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

There are no annotations, so the description carries the behavioral disclosure burden. 'Retrieve' implies a read-only operation, and the paging note signals that large responses are expected. However, it does not mention response format, error behavior, or performance considerations beyond paging, leaving some gaps.

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 filler. The core purpose is front-loaded and the paging guidance is directly relevant to safe usage. Every sentence earns its place.

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?

For a simple source-retrieval tool, the schema covers all parameters and the description adds paging context. There is no output schema, so return-value details are not specified, and error behavior is absent; still, the essentials needed to call it correctly are present.

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 input schema already provides 100% parameter coverage, including descriptions for program_name, startLine, and maxLines. The description adds no new parameter semantics beyond mentioning the paging parameters by name, so the baseline 3 applies.

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 and resource ('Retrieve ABAP program source code') and clearly distinguishes the tool from sibling object-specific tools like GetClass, GetTable, and GetTransaction. An agent knows exactly what this tool returns and which object type it targets.

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 gives explicit guidance for large programs: use startLine/maxLines to page instead of retrieving all at once. It does not explicitly mention alternatives among siblings, but the siblings are distinct object types, so the intended use case is reasonably clear.

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