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, and it discloses nothing: no indication of whether this is read-only or mutating, whether it returns guidance text or applies overrides, or what it changes.

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 single fragment is short, but this is under-specification rather than conciseness — the text exists only to label the tool, so there is no front-loaded useful content to speak of.

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 annotations, no output schema, two parameters with an unexplained enum, and a description that provides nothing. For a tool an agent must call correctly with an enum-valued 'focus' argument, this is wholly inadequate.

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?

Two parameters with only 50% schema description coverage: 'mode' has a terse schema description and 'focus' has none despite an enum of six values. With low coverage the description is required to compensate, and it adds zero information about either parameter.

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 only restates the tool name and slug ('ui.overrides.guide (ui-overrides)') plus a platform prefix. It never states what the tool actually does — produce guidance? return override configs? — so an agent cannot tell its behavior apart from siblings like flutter::ui.mode.recommend or flutter::app.scaffold.

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?

There is no when-to-use, when-not-to-use, prerequisite, or alternative-mentioned guidance of any kind. The agent is left to guess how this differs from the closely related flutter::ui.mode.recommend tool.

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