GetNodeStructureLow

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

With no annotations, the description carries the full behavioral burden. It discloses one useful trait (session can be carried over from GetSession to reuse the same connection) but says nothing about read-only nature, permissions, response shape, or what 'low-level' implies versus the higher-level variant.

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?

Three compact sentences, front-loaded with the '[low-level]' marker and purpose before the usage and session notes. No filler, though the bracketed tag is never explained.

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 6-parameter fetch tool with a nested session_state object and no output schema, the description is adequate but thin — it doesn't characterize the returned node structure or hierarchy depth, which an agent calling this for tree navigation would benefit from knowing.

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 100%, including subtle notes like node_id '0000' returning an empty body, so the schema already does the heavy lifting. The description only repeats the session_id/session_state usage, adding no format or semantics beyond the schema.

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?

States a clear verb+resource: 'Fetch node structure from ADT repository,' plus a use case ('object tree navigation and structure discovery'). However, it does not distinguish itself from near-identical siblings such as GetObjectStructureLow or GetObjectStructure, and the '[low-level]' tag is left unexplained.

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?

'Used for object tree navigation and structure discovery' implies the scenario but gives no when-to-use vs when-to-avoid guidance, and never names an alternative like GetObjectStructureLow. The GetSession/session-reuse note is helpful but is invocation mechanics, not selection guidance.

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