Godot Project Doctor

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions 'health checks' which implies a read/diagnostic operation, but doesn't disclose what data it inspects, whether it mutates anything (e.g., repairs found issues), what failure conditions look like, or what the output contains. With zero annotation coverage, this is a notable gap.

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 concise sentence with no wasted words. It front-loads the primary action ('Run health checks') and appends the secondary scope (bridge connectivity). It's appropriately minimal for a zero-parameter tool, though it could gain slightly from a clearer scoping phrase.

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?

With no annotations and no output schema, the description must carry all the burden. For a diagnostic tool of this nature, it doesn't explain what a successful or failing check looks like, what the return/report format is, or whether it can repair issues. A tool named 'doctor' implies diagnosis and possibly remediation, but the description only hints at running checks.

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 tool has 0 parameters and schema coverage is 100%, so there are no parameter semantics to explain. Per the rubric, 0 params equals a baseline of 4. The description correctly implies this is a no-argument diagnostic tool without needing to document parameters.

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 a specific verb+resource ('Run health checks against the project installation and bridge connectivity'). It's clear but somewhat ambiguous about what a 'health check' concretely covers — whether it validates the project files, the editor connection, or both. Among siblings it's reasonably distinct (no other sibling does 'health checks'), though it shares the project-doctor naming with the project info/status tools.

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 provides no guidance on when to use this tool versus alternatives. It doesn't say when to run health checks, what prerequisites exist (e.g., project must be loaded / editor must be connected), or how it relates to godot_project_info, godot_project_scan, or godot_editor_status. The 'bridge connectivity' part hints at a use case but lacks explicit context.

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