list_local_player_subsystems

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

Annotations already establish it as a safe, idempotent, non-destructive read, so the bar is lower. The description still adds real context: only 'live' (instantiated) subsystems are returned, they come from the editor world's GameInstance, and they span all local players.

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?

One sentence, leading with the verb and narrowing the scope in a single clause. No filler, no restatement of the tool name.

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 zero-parameter enumeration with no output schema, the description conveys the population being enumerated but not the return shape (e.g., whether instances, class names, or player associations come back) or how resulting handles feed into inspect_subsystem_instance. Adequate, with a small gap on return-value expectations.

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 tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. The empty schema is consistent with the description, which implies a global sweep with no filters.

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 ('Enumerate') and a tightly scoped resource ('ULocalPlayerSubsystem-derived instances across all local players in the editor world's GameInstance'). That scope distinguishes it from the generic sibling subsystem listings (list_subsystem_classes, list_subsystem_instances) without needing to name them.

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 precise scope implies when the tool applies, but the description never states when to prefer it over list_subsystem_instances, get_subsystem_instance, or is_subsystem_class_active. No exclusions or prerequisites are given, so the agent must infer routing from the resource phrasing alone.

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