adb_settings_get

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

No annotations exist, so description must carry transparency burden. It states 'Read' indicating non-destructive operation, but lacks details on permissions, error conditions, or device connection requirements.

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 concise sentence that effectively conveys the tool's purpose without unnecessary words or fluff.

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?

For a simple read tool, the description covers the essential purpose and namespace scope. It does not explain return values but given no output schema, this is acceptable. Minor omission: does not mention that the 'device' parameter is optional.

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% with descriptions for all three parameters. The description adds 'any namespace (system, secure, global)' which matches the enum, but provides no additional meaning beyond what the schema already offers.

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?

Description clearly uses verb 'Read' and resource 'Android settings value' from specific namespaces, distinguishing it from sibling tools like adb_settings_put which writes settings.

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 implies usage for reading settings but provides no explicit guidance on when to use, when not to use, or alternatives beyond the tool name itself.

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