query_ue_knowledge

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

With no annotations, the description carries the full burden of behavioral disclosure. It states the tool performs a search, implying a read-only operation, but it does not mention return format, pagination, result limits, or whether it returns snippets, summaries, or references. This is a significant gap for a tool with no output schema.

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, front-loaded sentence with no filler or redundancy. It efficiently communicates the tool's purpose and scope, entirely appropriate for a search tool.

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?

While the tool is simple (one parameter, low complexity), the description does not clarify what the search returns or how results are structured, which is needed since there is no output schema. It also does not relate to sibling knowledge tools, leaving some contextual ambiguity. However, for a basic search action, the core function is adequately conveyed.

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 coverage is 100%: the sole parameter 'query' is described as 'Search query (keywords, system names, or tags)'. The tool description adds no additional meaning to the parameter beyond what the schema already provides, so the baseline score of 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?

The description clearly states a specific verb ('Search'), a resource ('UE5.6+ knowledge database'), and the scope ('Unreal Engine systems, features, and best practices'). This distinguishes it from sibling tools that focus on code, assets, actors, or blueprint operations, making its purpose unambiguous.

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 implies usage when one needs general Unreal Engine information, but it does not explicitly state when to use this tool versus alternatives like get_ue_systems_by_tag or get_related_ue_systems. No exclusions or alternative recommendations are provided, so guidance is implied rather than explicit.

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