GetObjectStructure

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

The description includes the [read-only] tag, indicating safe behavior, but no annotations exist to confirm. No further behavioral traits (like permissions, side effects, or performance) are disclosed, leaving some ambiguity.

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 a single, concise sentence with no unnecessary words. It is front-loaded and easy to parse, earning its place efficiently.

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 no output schema, the description mentions 'compact JSON tree' which hints at return format. For a simple retrieval tool with well-documented parameters, this is mostly complete, though a bit more detail on the tree structure would help.

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 covers both parameters with clear descriptions (objecttype and objectname). The description does not add any extra meaning or constraints beyond the schema, achieving baseline adequacy.

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 retrieves ADT object structure as a compact JSON tree, using a specific verb and resource. It distinguishes itself from sibling tools like GetObjectStructureLow (not listed directly, but implied) by focusing on a compact tree format.

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 no guidance on when to use this tool versus alternatives such as GetObjectStructureLow or GetClass. It lacks context about scenarios where this tool is preferred or when to avoid it.

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