Android Component Status Validator

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

Read-only annotation is consistent with description. Description adds valuable behavioral context: it prevents use of removed/deprecated APIs, and lists known failures. No contradictions.

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?

Single paragraph with clear front-loading of purpose and usage. Could be slightly more structured (e.g., bullet points) but no unnecessary sentences.

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?

Covers purpose, usage, examples, and return info (status, replacement, migration notes, link). Lacks details on return format or error handling, but sufficient for a simple validation tool.

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 already fully describes parameter with 100% coverage. Description reinforces example values but does not add new semantic information beyond schema.

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?

Clearly states it checks stability/deprecation/removal of Android/Kotlin components. Distinguishes from sibling tools like android_api_level_check by focusing on API status rather than API level. Provides specific examples of known failures.

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?

Explicitly instructs to call before using any class from android.*, androidx.*, or kotlin.*. Provides context about AI tool failures and lists specific examples of removed/deprecated APIs.

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