Android Large Screen & Adaptive Layout Guide

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

Annotations already declare readOnlyHint=true, indicating safe read-only operation. The description reinforces this by calling it a 'reference,' but does not add additional behavioral context like rate limits, authentication needs, or output format. The description does not contradict annotations.

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 paragraph that front-loads the main purpose and lists key topics. It is reasonably concise, though a few more sentences could be trimmed without losing value. Keywords at the end aid scanning.

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 complexity (a reference guide) and the simple input schema (one optional param with no output schema), the description adequately covers what the tool does and how to use it. It could mention the return format (e.g., returns text/guidance) but is otherwise complete for an agent.

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 coverage is 100% (one param with description). The description adds extra meaning beyond schema by listing example topics (e.g., 'windowsizeclass', 'NavigationSuiteScaffold') and explicitly stating 'Leave empty for index,' which helps the agent know how to use the parameter effectively.

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 it is a complete reference for building Google Play-compliant large screen apps, covering specific topics like WindowSizeClass, two-pane navigation, and foldable detection. It distinguishes itself from sibling tools by focusing on large screen and adaptive layouts, with explicit scope (tablets, foldables, ChromeOS).

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 gives explicit when-to-use guidance: 'Call before building any multi-screen layout, navigation, or when targeting tablets and foldables.' However, it does not mention when not to use this tool or suggest alternative sibling tools, such as android_navigation3_guide or android_scalability_guide.

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