emulator_get_rendering_defects

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

No annotations are supplied, so the description carries the full disclosure burden. 'Inspect' implies a read-only operation, but the description never states side effects, permission/liveness requirements, or how results are scoped or truncated. For a zero-parameter-required diagnostic tool, this leaves meaningful behavioral gaps.

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?

A single front-loaded sentence with no filler; both clauses carry information. The parenthetical is slightly cryptic but earns its place by explaining why skipped draws matter.

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?

The tool is simple (two optional params, no nested objects) and the description names the two categories of findings, which partially substitutes for the absent output schema. It still omits the return shape (counts vs. event list) and any operational preconditions, which is a real gap given no annotations and no output schema.

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 tail_events and emulator_dir are already documented in the schema, and the baseline of 3 applies. The description adds no semantics about the event window or the path parameter beyond what the schema states.

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 gives a specific verb ('Inspect') and two concrete resources: skipped draws (framed as a zero-stutter indicator) and Vulkan validation/compilation errors. That is enough to distinguish it from siblings like emulator_get_performance or emulator_get_live_logs, though it never names a sibling explicitly.

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 when-to-use or when-not-to-use guidance is given, and no prerequisites are stated (e.g., must the emulator be running, is a capture required?). The closest thing to guidance is the parenthetical 'zero-stutter indicator', which hints at a stutter-diagnosis scenario but leaves routing between it and emulator_get_shader_stats or emulator_get_performance to inference.

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