ue_create_blackboard

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

The description discloses the default key behavior but omits critical details: no mention of whether the asset overwrites, is saved, requires a package, or has other side effects. With no annotations, this lack of disclosure is significant.

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 and front-loaded sentence that efficiently conveys the action and a key detail. No unnecessary words.

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?

Without annotations, an output schema, or parameter details, the description is insufficient for correct invocation. It does not relate to sibling blackboard tools or explain the expected workflow.

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?

With 0% schema description coverage, the description does not explain the 'name' and 'package_path' parameters. The agent gains no additional meaning beyond the field names.

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 creates an empty Blackboard Data asset and specifies the default SelfActor key, making the purpose unambiguous and distinguishing it from siblings like ue_blackboard_add_key.

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?

No guidance is provided on when to use this tool versus alternatives. For instance, it does not mention that adding keys should be done with ue_blackboard_add_key or that this tool is for initial asset creation.

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