get_include_path

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

No annotations are provided, so the description carries full burden. It states the function but does not disclose edge cases (e.g., what happens if the name is invalid, case sensitivity, or whether multiple results exist). Minimal behavioral context beyond the basic operation.

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 short and to the point, with the main action front-loaded. It could be slightly more structured by integrating the parameter explanation into the first sentence, but overall it is efficient and avoids 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?

The description is adequate for a simple tool with one parameter and an output schema (which covers return format). However, it lacks information about error handling or validation, leaving some gaps about tool behavior in edge cases.

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?

Despite 0% schema description coverage, the description provides examples (e.g., 'AActor', 'FHitResult') and clarifies the parameter expects a class/struct/type name, adding significant meaning beyond the schema's bare type definition.

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?

Clearly states the tool retrieves the #include path for Unreal Engine classes/structs/types. The verb 'Get' and resource 'include path' are specific, and it is distinct from siblings like 'get_class_reference' or 'search_unreal_api'.

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?

Implied usage from sibling list but no explicit guidance on when to use this over alternatives. Lacks any 'when not to use' or prerequisite information, though the purpose is straightforward.

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