Flutter Inspector MCP Server

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

No annotations are provided, so the description carries full burden. It mentions 'Toggle' which implies a mutation operation, but doesn't disclose behavioral traits like required permissions, side effects, or what happens when toggling (e.g., immediate effect, app restart needed). It also doesn't mention rate limits, error conditions, or response format.

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 extremely concise—a single sentence that directly states the tool's purpose with zero wasted words. It's front-loaded with the core functionality and includes the exact RPC identifier. Every part earns its place.

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 no annotations and no output schema, the description is incomplete for a mutation tool. It doesn't explain what 'debugging' entails, what physical shape layers are, what the toggle affects, or what the tool returns. For a tool that modifies app state, more context about behavior and outcomes is needed.

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 100%, so the schema fully documents both parameters ('enabled' and 'port'). The description adds no additional parameter semantics beyond what's in the schema. Baseline score of 3 is appropriate since the schema does all the work.

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 the tool's purpose: 'Toggle physical shape layers debugging' with the specific resource 'ext.flutter.debugDisablePhysicalShapeLayers'. It uses a precise verb ('Toggle') and identifies the exact debugging feature, but doesn't explicitly differentiate from sibling tools like 'debug_disable_clip_layers' or 'debug_disable_opacity_layers' beyond the different feature name.

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. The description only restates the tool's function without mentioning context, prerequisites, or comparisons to sibling debugging tools. It lacks any 'when-to-use' or 'when-not-to-use' information.

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