ios_logs

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

With no annotations, the description carries the full behavioral burden. It discloses only one trait — that capture is time-bounded to N seconds — and says nothing about whether the call blocks for that duration, where logs are returned or written, or what happens if the device is unreachable.

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 front-loaded sentence with no filler, which is structurally sound. However, at this length it reads as under-specification rather than true conciseness, since key facts (output destination, defaults) were dropped rather than compressed.

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?

No output schema, no annotations, and zero parameter documentation mean the description is the only source of truth, and it omits defaults, output format, and device-targeting behavior. For a tool that likely has side effects (writing log files), that is a meaningful shortfall.

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% for both parameters. The description hints that 'seconds' controls duration, but never names it, gives no default (the param is optional) or units beyond the implicit 'seconds', and the 'device' parameter is entirely undocumented in both schema and 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?

The description pairs a specific verb ('抓' / capture) with a specific resource ('采集器运行日志' / collector runtime logs) plus a scope ('N 秒'), so an agent knows it triggers a timed log capture. It does not, however, differentiate itself from neighbours such as ios_env_check or sync_status, which also touch device state.

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 reach for this tool versus ios_env_check, ios_build, or ios_install, and no stated prerequisites (e.g. a connected/installed device). The reader must infer the whole usage context from the tool name alone.

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