get_project_context

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

With no annotations, the description carries the full burden. It discloses the 5-second cache behavior and lists the exact contents returned, which is useful. However, it does not explicitly state read-only behavior, failure modes, or any side effects, though a retrieval tool implies safety.

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 compact and front-loaded: the core behavior is in the first sentence, followed by a useful bulleted content list, a KB reference, and an example. Every element earns its place with no redundancy.

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?

An output schema exists and the description lists returned data fields, so return semantics are reasonably covered. The main gap is the undocumented force_refresh parameter and the absence of explicit usage guidance, which leaves the tool slightly incomplete for a fully self-sufficient definition.

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 single parameter force_refresh has 0% schema description coverage, and the description never directly explains how it works. The mention of the 5-second cache hints that force_refresh likely bypasses the cache, but the agent must infer this rather than read it explicitly.

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 and resource: 'Return the current Unreal project/editor context' and enumerates the included fields. It is specific enough to be distinguished from most sibling tools, though it does not explicitly name or contrast any sibling.

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 such as get_onboarding_context, get_server_info, or other context-gathering tools. There is no explicit when/when-not guidance; only the KB link, which points to general rules rather than usage criteria.

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