verify.collect_evidence

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

No annotations are provided, so the description must carry the full behavioral burden. It mentions 'where available,' hinting at graceful degradation, but does not disclose what happens when evidence types are missing, how failures are reported, or whether it creates files or returns data.

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 a single efficient sentence with no filler, and the key scope ('collect evidence') is front-loaded. It loses a point because it is so terse that it omits essential context, but its brevity is not wasteful.

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 tool with five unannotated parameters and no output schema, the description should explain what inputs the tool needs and what the agent gets back. It covers the general intent but is incomplete for safe invocation; an agent could not reliably choose parameter values.

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 0% and the description names none of the five parameters (prefix, serial, serverUrl, sessionId, packageName). An agent cannot infer what these parameters mean, which are needed for which evidence type, or how they combine.

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 a specific verb ('collect') and resource ('evidence'), enumerating screenshot, page source, and logcat. However, it does not distinguish itself from siblings like device.capture_screenshot, appium.get_page_source, or device.pull_logs, which overlap in function.

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?

No guidance is given on when to use this tool versus sibling evidence-collection tools. The description implies a batch evidence-gathering role, but it never states prerequisites (e.g., active Appium session, connected device), fallback ordering, or exclusions.

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