Sap Expand Tree Node

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

Annotations mark this as non-read-only but non-destructive, and the description usefully explains the actual effect: children become visible and require a follow-up read to inspect. It does not mention whether expanding an already-expanded node is a no-op or errors, nor whether it scrolls/loads lazily, but the core state change is disclosed.

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 short sentences with the action stated first and the follow-up second; no filler and nothing redundant with 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?

An output schema exists so return values need not be described, and the follow-up guidance covers the agent's next step. However, for a tool whose two required parameters are entirely undocumented in the schema, the description should have clarified tree_id and node_key formats, which it does not.

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 0% for both required parameters, so the description must carry the burden and largely does not. Saying 'a folder node' usefully implies node_key must reference an expandable/folder node rather than a leaf, but tree_id is never explained at all, leaving half the parameters undocumented anywhere.

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?

Specific verb (expand) plus resource (folder node in a tree control) plus the effect (reveal its children). It is clearly distinguishable from siblings like sap_collapse_tree_node, sap_select_tree_node, and sap_get_tree_node_children without opening any schema.

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 second sentence gives explicit follow-up guidance: after expanding, call sap_get_tree_node_children or sap_read_tree to see the children, which tells the agent the correct tool sequence. It does not explicitly state when not to use it (e.g., already-expanded nodes, or use sap_collapse_tree_node to reverse), but the context is clear.

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