GetPackage

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

With no annotations provided, the description carries the burden of behavioral disclosure. It reveals that output is a serialized listing that can be large and that paging may be needed, which is useful behavioral context beyond the schema. It does not mention permissions or error behavior, but for a simple retrieval this is a reasonable level of transparency.

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 main action is front-loaded, and the second sentence adds operational guidance about paging. Every word 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?

The tool is simple (one required parameter, two optional paging parameters) with no output schema. The description covers the core purpose and the paging behavior. It could also state the output format more explicitly, but the schema descriptions for startLine/maxLines already cover edge cases like hasMore=false.

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 description coverage is 100%, so the baseline is 3. The description adds meaning by clarifying that startLine/maxLines are for paging large output and that the result is a listing, which supplements the schema's parameter notes.

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 states a clear verb and resource: 'Retrieve ABAP package details.' It is distinct from the many sibling 'Get*' tools by naming the specific object type. However, it does not explicitly differentiate itself from those siblings beyond the object name, and 'details' is somewhat vague.

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 usage guidance for paging ('Use startLine/maxLines to page large serialized package listings.') but does not state when to choose this tool over alternatives like GetTransaction or GetClass. The usage context is implied by the sibling structure rather than explicitly explained.

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