get_semantic_labels

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

With no annotations provided, 'Read' clearly signals a non-mutating, read-only operation. The description adds useful behavioral context by naming the exact API version (6.0.1) and expanding scope to include legacy semantic labels, which is beyond what the resource name alone conveys.

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, tight sentence with no fluff. It front-loads the verb and resource, then adds the legacy-label qualifier. Every word carries meaning.

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 is simple and has an output schema, but the required prim_path paramater is undocumented and no usage guidance or exclusions are provided. An agent could invoke the tool with an incorrect prim_path because the description does not specify what path is expected or how labels are scoped.

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%, and the description does not explain the role of the required prim_path parameter or the optional command_id/idempotency_key parameters. The tool name and description imply that prim_path identifies a prim, but that is left to inference rather than stated.

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 uses a specific verb 'Read' with a specific resource: 'Isaac Sim 6.0.1 LabelsAPI taxonomies and labels'. This clearly distinguishes it from the sibling set_semantic_labels, and the mention of 'legacy semantic labels' further scopes its behavior.

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 states what the tool does but offers no guidance on when to use it as opposed to siblings like get_typed_attribute, get_prim_info, or set_semantic_labels. There are no explicit when/when-not conditions or alternative tool names.

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