Get Mobile App Logs

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering safety. The description adds meaningful behavioral context: platform-specific filtering (UID vs executable) and bounded recency, which complements the annotations without contradiction.

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 two concise sentences: first states the overall purpose, second adds crucial platform-specific detail. No wasted words, front-loaded with key action.

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 structure (4 params, output schema exists), the description covers the core purpose and platform nuance. It could note potential log length truncation or permissions, but overall it's sufficiently complete for selection and invocation.

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 description coverage is low (25%: only device has a description). The description compensates partially by explaining that logs are 'bounded recent' (relates to maxLines and sinceMinutes) and that appId identifies the app. However, it does not detail parameter ranges, defaults, or how the platform filtering maps to parameters.

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 returns bounded recent logs for one installed app, with specific verb 'return' and resource 'logs'. It also distinguishes from siblings by focusing on logs for a single app, which is different from listing devices or managing app lifecycle.

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 use when needing recent logs for a specific app, but no explicit when-not-to-use or alternative tools are mentioned. The sibling list suggests alternatives like mobile_list_devices for device info, but guidance is absent.

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