lookup_android_source_code

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. It mentions that it returns 'Detailed information about the source code location and content', but does not explicitly state that it is read-only or disclose any potential side effects or prerequisites, leaving some ambiguity.

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 compact with a clear structure: a one-sentence purpose, an Args section with examples, and a Returns line. Every sentence adds value and there is no redundant or verbose content.

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 two-parameter lookup tool with an output schema, the description covers the purpose, parameters, and return behavior adequately. The existence of an output schema means detailed return structure need not be repeated, and the description suffices.

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 provides basic types and defaults but no descriptions (0% coverage). The description compensates by giving keyword examples ('SEAT', 'HVAC', 'vehicle properties') and clarifying that category is a focus area with default 'vhal', adding meaningful context beyond the 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?

The description states 'Lookup Android source code for a given keyword' which clearly identifies the verb (lookup) and resource (Android source code), and provides examples of keywords. It distinguishes from siblings such as generate_vhal_implementation_code and analyze_vhal_implementation, which focus on generation and analysis rather than lookup.

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 does not provide any guidance on when to use this tool versus its siblings, such as discover_related_properties or summarize_vhal. It simply states what it does without mentioning alternatives or exclusions.

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