GetStructure

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

No annotations are provided, so the description carries the burden of behavioral disclosure. It discloses that large structures may require paging and implies a default behavior of retrieving all lines, but it does not mention read-only guarantees, error conditions, or response format. The paging hint adds some value but is not comprehensive.

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?

The description is two sentences with no wasted words. The purpose is stated first, followed by the key usage guidance. It is perfectly front-loaded and efficient.

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 retrieve tool with no output schema, the description gives the essential usage pattern (paging) and the required parameter is clear from the schema. It does not describe the return structure, but that is not critical for calling the tool correctly. The description is adequate for an agent to invoke it appropriately.

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 has 100% coverage with clear descriptions for all three parameters. The description reinforces the paging behavior but does not add new semantic detail beyond what the schema provides. It mentions the paging parameters together, but the schema already explains their meaning and defaults.

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 ('Retrieve') and resource ('ABAP Structure'), which is clear and distinguishes it from sibling tools like GetTable or GetCDSView. It does not explicitly contrast with alternatives, but the name and description make the target object type unambiguous.

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 explicit guidance on when to use paging (for large structures) and directs the agent to use startLine/maxLines instead of retrieving everything at once. It does not mention when to choose this tool over siblings, but the object-type specificity makes that choice obvious.

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