Android 17 / API 37 Compliance

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

Annotations already declare readOnlyHint=true, indicating a safe read operation. The description adds context on the information provided (breaking changes list) but does not elaborate on other behavioral traits like return format or limitations. It 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 dense but well-structured. It uses numbered lists and a 'Topics:' section for clarity. While somewhat lengthy, every sentence serves a purpose given the complex subject matter. It is concise enough for the information it conveys.

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 simple parameter and no output schema, the description provides sufficient context: what the tool does, how it differs from a sibling, and available topics. It could mention the return format, but it's not critical for a information-retrieval 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?

The single parameter 'topic' is fully described in the input schema with enumerated options. The tool description adds explanatory details for each topic, providing more meaning beyond the schema's brief list. Since schema coverage is 100%, baseline is 3, and the description adds value, a 4 is justified.

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 the tool's purpose: providing information about Android 17 API 37 compliance, specifically breaking changes not covered by android_api36_compliance. It lists specific topics, making the resource clear and differentiating it from the sibling tool.

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 explicitly mentions that it contains breaking changes NOT covered by android_api36_compliance, guiding the agent to use that sibling for API 36 changes. It also lists topics like 'overview', 'checklist', etc., providing context on when to use each. However, it does not explicitly state when not to use this tool.

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