Get Logs

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

No annotations provided, so the description carries full burden. It describes the output format and filtering options but does not disclose potential behavioral traits like rate limits, performance impact, or permission requirements. The description is accurate but lacks depth.

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 sentences: first states purpose, second covers filtering and output. Efficient and front-loaded, but could be more concise by removing redundancy (e.g., 'Retrieve recent Android logcat entries' vs 'from the device').

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 no output schema, the description adequately describes return format. However, it lacks guidance on the number of returned entries, error handling, or logcat command equivalency. Still, it is sufficient for basic use.

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 100%, so the schema already documents all four parameters. The description adds meaning by explaining the log level mapping (V=Verbose, etc.) and tag filter usage, but does not go beyond confirming the schema's details. Baseline 3 plus extra context for the level enum explanation.

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 retrieves recent Android logcat entries, specifying the source (Android device) and output format (structured JSON with timestamp, PID, TID, level, tag, message). It distinguishes from sibling tools like get_device_info or get_ui_elements.

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 usage for debugging or log analysis but does not explicitly state when to use this tool vs. alternatives like extract_text or find_element. No exclusionary guidance is provided.

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