godot_csharp_check

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

No annotations are present, so the description must fully disclose behavior. It only labels the tool as a 'compile/syntax check' without explaining side effects, error handling, or what each action does concretely (e.g., whether build modifies files).

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 very short (one sentence) but uses ambiguous punctuation and parentheses that reduce readability. It's concise but not well-structured or polished.

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 the tool's two parameters and no output schema, the description fails to explain return values, error conditions, or required parameter formats. The agent lacks enough context to use the tool reliably.

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 must compensate. It mentions actions and hints at parameters ('project?', 'source?/path?') but does not clarify the 'params' field or specify valid values, leaving agent guessing.

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 states 'C# compile/syntax check' and lists three actions (info, build, syntax), providing a clear verb and resource. However, the question marks and parentheses create ambiguity about parameters and exact behavior, reducing specificity.

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 given on when to use this tool versus siblings like godot_script or godot_exec. There are no usage contexts, exclusions, or comparisons provided.

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