check_ui_fluidity

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. The phrase 'Returns' implies a read-only, non-destructive operation, which is useful. However, it does not disclose whether the tool executes ADB commands or merely returns them as text, nor does it mention any potential side effects, permissions, or environment requirements. This is a moderate level of 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 concise, consisting of a single sentence plus a brief parameter hint. It avoids unnecessary fluff and front-loads the key information about what is returned. The parameter hint is slightly redundant with the schema but serves as a quick reference. Overall, it is appropriately sized and structured.

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 that the tool has no output schema and no annotations, the description is responsible for providing complete context. It lists four categories of returned information but does not elaborate on what 'frame rate thresholds' or 'ACR crash analysis' entail, nor how to interpret the results. The presence of sibling tools like fluidity_debug_workflow suggests there may be related workflow logic that this description does not address. Thus, while it covers the basics, it leaves gaps in context.

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 schema has one parameter 'screen' with an enum of allowed values, and schema_description_coverage is 0%. The description repeats the enum values ('screen: home|player|search|all') but adds no new meaning beyond what the schema already provides. It does not explain the purpose of the parameter, its optionality, or how it affects the output. Thus, the description adds little value for understanding the 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 clearly states that the tool returns frame rate thresholds, ADB commands, Macrobenchmark templates, ACR crash analysis, and screen-specific guidance. This is a specific verb-resource pairing that conveys the tool's purpose. However, it does not explicitly distinguish itself from sibling tools like verify_ui or fluidity_debug_workflow, which may have overlapping functionality.

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 no guidance on when to use this tool versus alternatives. It only lists what the tool returns without any context on selection criteria, prerequisites, or exclusions. Since sibling tools like get_ui_compose_standards and fluidity_debug_workflow exist, this lack of guidance makes it hard for an agent to know when to choose this tool.

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