get_subsystem_class_info

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

Annotations already declare the safe read-only/idempotent profile, and the description adds the concrete return payload (parent_chain, lifetime, is_abstract), which is genuinely useful behavioral context. It does not, however, describe failure behavior when a class name is not found or how the inheritance chain is resolved.

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 sentences, front-loaded with the purpose and followed by the return shape. Every element earns its place, especially the return block given there is no output 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?

With annotations covering the safety profile and the description documenting the return object in lieu of an output schema, an agent has what it needs to call the tool. The only gap is absence of any failure-mode or usage-context note.

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%; the single class_name parameter is fully documented in the schema (short name or /Script/ path). The description adds no further parameter meaning, so the baseline 3 applies.

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 specific verb ("Read") plus a specific resource ("class metadata and the full USubsystem inheritance chain for a subsystem class"). This distinguishes it implicitly from instance-siblings like get_subsystem_instance, but no sibling is named explicitly, so it falls just short of the top band.

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?

There is no guidance on when to use this versus the adjacent subsystem tools (get_subsystem_instance, is_subsystem_class_active, list_subsystem_classes). It only describes what is returned, leaving the agent to infer selection criteria from tool names.

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