flutter_core_invert_oversized_images

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions 'Toggle' and 'for debugging', which implies a mutation operation, but it doesn't disclose critical traits like whether this requires specific permissions, if changes are reversible, potential side effects, or rate limits. For a mutation tool with zero annotation coverage, this is a significant gap in transparency.

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, efficient sentence ('RPC: Toggle inverting of oversized images for debugging') that is front-loaded with the core action and context. It wastes no words and is appropriately sized for the tool's complexity, earning a high score for conciseness.

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 moderate complexity (2 parameters, no output schema, no annotations), the description is somewhat complete but has gaps. It covers the basic purpose and debugging context but lacks details on behavioral traits, usage alternatives, and output expectations. With no output schema, it should ideally hint at return values or effects, which it doesn't, making it minimally adequate but not fully comprehensive.

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 100% description coverage, with clear documentation for both parameters ('enabled' and 'port'). The description adds no additional parameter semantics beyond what the schema provides, such as explaining the 'inverting' process or default port usage. Given the high schema coverage, the baseline score of 3 is appropriate, as the schema does the heavy lifting.

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 as 'Toggle inverting of oversized images for debugging' with a specific verb ('Toggle') and resource ('inverting of oversized images'), making it understandable. However, it doesn't explicitly differentiate this from sibling tools like 'debug_paint_baselines_enabled' or 'flutter_core_brightness_override', which also appear to be debugging toggles, so it misses full sibling distinction.

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 minimal guidance by mentioning 'for debugging', which implies usage in debugging scenarios, but it doesn't specify when to use this tool versus alternatives (e.g., other debugging tools in the sibling list) or any prerequisites. No explicit when/when-not or alternative tools are named, leaving gaps in usage context.

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