GetInclude

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

Annotations already cover read-only, idempotent, and non-destructive behavior. The description adds a useful behavioral hint about paging large includes, but it does not disclose details like default line limits, byte caps, or what happens when paging is omitted. It adds some context beyond annotations but not a rich behavioral picture.

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, no filler. The first sentence states the core purpose; the second provides actionable paging guidance. 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 a simple read-only retriever, and annotations cover safety. The schema fully documents parameters, and the description gives the key paging context. It is complete enough for correct invocation, though it does not describe return formatting or error behavior explicitly.

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 coverage is 100%, so the baseline is 3. The description adds meaning by explaining why startLine and maxLines matter together: they are for paging through large includes. This goes beyond individual parameter descriptions and tells the agent how to combine them effectively.

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 specific verb and resource: 'Retrieve ABAP Include Source Code.' It is distinct from sibling tools like GetProgram or GetFunction because it names the exact ABAP object type being retrieved. The paging hint reinforces the purpose without ambiguity.

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 clear guidance for large includes: use startLine/maxLines to page instead of retrieving everything at once. It does not explicitly compare GetInclude with sibling tools or state when not to use it, so it falls short of full alternative-selection guidance.

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