Get recent logs

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

Annotations already mark readOnlyHint=true; description adds that this is a one-shot (not continuous) operation and that app filtering requires the app to be running. This is useful context beyond the safety hint, though it doesn't detail output limits.

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 sentence that is front-loaded with the action and resource, with no wasted words.

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 read-only log dump with four optional, well-documented parameters and no output schema, the description conveys the essential behavior and constraints. It doesn't mention return format or default line count, but the schema covers defaults.

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?

Input schema has 100% coverage for all four parameters, so the description doesn't need to explain each. It adds only generic filtering context and the 'must be running' constraint, which is largely already in the appId schema description.

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 uses specific verb 'dump' with resource 'recent logcat lines' and optional filters. It clearly distinguishes from sibling tools like start_log_capture (continuous capture) and get_crash_logs.

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?

States one-shot nature and filtering by app (must be running) and/or tag, giving clear context for use. It does not explicitly name alternatives or when-not-to-use, so not a 5.

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