ios.collect_logs

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states that logs are collected into artifacts, without saying whether the operation is read-only, whether a simulator must be booted, whether existing artifacts are overwritten, or what 'recent' means.

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 compact sentence that starts with the action, so it is not verbose. However, it is under-specified rather than deliberately structured; it lacks any separate guidance, parameter hints, or prerequisites.

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?

With four undocumented optional parameters, no annotations, and no output schema, the description leaves critical invocation details unknown. An agent cannot reliably determine how to select a device, filter logs, set a time range, or understand what artifacts will be produced.

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?

All four parameters (last, device, prefix, predicate) have no schema descriptions and 0% schema coverage. The description does not explain or even mention any of these parameters, leaving the agent without the information needed to set filters, targets, or limits.

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 names a specific verb ('collect') and resource ('recent simulator logs'), so an agent can tell this is an iOS simulator log-collection tool. It does not explicitly differentiate from siblings like device.pull_logs or build.collect_build_logs, but the 'simulator' scope is reasonably clear.

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?

There is no guidance on when to use this tool versus alternatives such as device.pull_logs, verify.collect_evidence, or build.collect_build_logs. No preconditions, exclusions, or selection criteria are stated, so an agent must guess when this is the right tool.

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