uninstall_exporter

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

The description only says 'Remove', implying a destructive operation. No annotations are provided to clarify side effects, such as whether files are deleted or if the tool fails gracefully when the exporter is not present. Behavioral traits are not disclosed beyond the verb.

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, clear sentence with no extraneous words. While it could be more informative, it is appropriately concise for a straightforward operation.

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?

No output schema exists, so the description should explain what the tool returns (e.g., success confirmation, list of removed files). It does not. Additionally, it lacks information on the dry_run parameter's effect or error handling, leaving gaps for complex usage.

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 description coverage is 0%. The description does not explain the purpose of the two parameters (project_path, dry_run) or how they affect tool behavior. For example, what does dry_run do? The description adds no value beyond the raw schema.

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 'Remove managed Godot capture exporter scripts from the target project' clearly states the action (remove) and the resource (managed Godot capture exporter scripts). It effectively distinguishes this tool from siblings like ensure_exporter_installed, which does the opposite.

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 vs alternatives. While sibling tools exist (e.g., ensure_exporter_installed), the description does not mention scenarios where uninstalling is appropriate or any prerequisites. The agent must infer usage from context alone.

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