GetStructuresList

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

The description highlights the key behavioral trait 'read-only' and mentions recursion and tree output. It also notes in the schema that include_extensions uses slower where-used lookups. However, with no annotations provided, it does not fully disclose authorization needs or rate limits.

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?

Single sentence that conveys essential information without any extraneous text. The '[read-only]' prefix effectively front-loads the most critical behavioral note.

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 has 4 parameters and no output schema. The description explains the purpose but does not detail the return format beyond 'as a tree', nor does it cover error conditions or edge cases. More specificity about the tree structure would improve completeness.

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% with all parameters well-described. The description adds overall context (recursive tree listing) but does not provide additional semantics beyond the schema's per-parameter descriptions. Baseline score of 3 is appropriate.

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 clearly specifies the action (recursively list) and the resource (structures embedded in an ABAP structure via INCLUDE/append), and indicates the output format (as a tree). This distinguishes it from siblings like GetStructure (single) or GetIncludesList (flat list).

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?

No explicit guidance on when to use this tool versus alternatives. The '[read-only]' hint is present but does not help the agent decide between this and other list/describe tools. Siblings like GetIncludesList and GetObjectStructure are not mentioned.

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