GetNodeStructureLow

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

No annotations are provided, so the description carries full burden for behavioral disclosure. It does not state whether the operation is idempotent, safe, or has side effects. It only implies it is a read operation for navigation, but fails to disclose input validation behavior, error handling, or any restrictions.

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 extremely concise—two sentences, no fluff. The first sentence states the purpose, the second adds session context. Every word adds information, and it is front-loaded with the core action.

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?

Given the tool has 6 parameters including nested objects and no output schema, the description does not explain the relationship between node_id and parent parameters, nor what the return value contains (e.g., child nodes, descriptions, structure). It is adequate for a simple tool but lacks completeness for a low-level navigation tool.

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?

All parameters are described in the input schema (100% coverage), so the baseline is 3. The description adds value by explaining session_id and session_state can be reused from GetSession to maintain the same session, which provides context beyond the schema's 'optional' and 'required' tags.

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 states the tool fetches node structure from ADT repository for object tree navigation and structure discovery. It uses a specific verb ('Fetch') and resource ('node structure from ADT repository'), and the '[low-level]' prefix distinguishes it from higher-level siblings like 'GetObjectStructure'.

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 mentions using session_id and session_state from GetSession for session reuse, which provides some guidance. However, it does not explicitly state when to use this tool vs alternatives like 'GetObjectStructureLow' or 'GetObjectNodeFromCache', nor does it include when-not-to-use or prerequisite conditions.

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