Validate Enfusion Resources

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the tool is known to be read-only and closed-world. The description adds transparency by detailing exactly what is validated (meta files, GUIDs, paths, etc.), going beyond the annotations without contradicting them.

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 two sentences (EN and DE), front-loaded with the English version. It is concise and to the point, though the German repetition could be trimmed. Overall, it is efficient and readable.

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?

Given a simple input (one parameter) and no output schema, the description lists what the tool checks but does not explain the return format (e.g., list of issues, success/failure). It covers the scope of validation adequately but lacks detail on expected output, making it mildly incomplete.

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 input schema has a single required parameter 'project' with no description. Schema description coverage is 0%, and the tool description does not explain what 'project' means (e.g., project name or path). The description adds no semantic meaning to the parameter.

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 uses specific verbs ('Check') and lists concrete resources (local .meta files, GUID uniqueness, resource paths, missing metadata, mismatches). This clearly distinguishes it from sibling tools like inspect_project or search_workspace, which serve different purposes.

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 states what the tool checks but provides no guidance on when to use it versus alternatives (e.g., inspect_project for project structure, search_workspace for broader search). No when-not or explicit context is given, so the usage is implied but not clarified.

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