GetFunctionGroup

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

Annotations already cover the safety profile: readOnlyHint, idempotentHint, and non-destructive. The description adds useful context about paging large function groups, but the paging semantics (hasMore, byte cap, EOF behavior) are already documented in the schema. It doesn't disclose return format, but none is needed for a straightforward read operation.

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 waste: the purpose is stated first, followed by the most important operational guidance about paging. Every sentence earns its place, and nothing in the description duplicates the schema.

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 read-only retrieval tool with full schema coverage and read-only annotations, the description covers the essential usage. It doesn't describe return values, but the absence of an output schema and the obvious nature of 'source code' make this acceptable.

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%, with all three parameters documented in detail including default startLine and byte cap behavior. The description reinforces the paging use case but doesn't add semantic information beyond what the schema already provides.

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 'Retrieve' as a specific verb and names the exact resource, ABAP Function Group source code. While it doesn't explicitly distinguish itself from siblings like GetFunction or GetProgram, the tool name and resource are unambiguous enough that an agent can identify its target.

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 clear operational guidance on using startLine/maxLines for large function groups. However, it doesn't state when to prefer this tool over alternatives like GetFunction or GetInclude, nor does it mention any exclusions or prerequisites.

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