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

No annotations exist, so the description carries the full behavioral burden, and it carries it well: it discloses that capture is live and timing-sensitive, that output is voluminous ('hundreds of lines per second,' so unfiltered captures are mostly noise), and what kinds of failures appear (crashes on launch, permission denials, startup failures). It stops short of describing output format, blocking behavior, or resource impact, which keeps it from a 5.

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 dense paragraph with no wasted sentences; purpose, differentiation, filtering guidance, timing, and prerequisite each earn their place. The most important scoping constraint is front-loaded ahead of the parameter guidance.

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 5-parameter tool with no annotations and no output schema, the description covers the critical usage context: what the log contains, how to filter the noise, when to capture, and when to use a sibling. Remaining gaps (return format, truncation, blocking semantics) are minor next to the strong contextual coverage.

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 coverage is 100%, so the baseline is 3; the description adds genuine value by explaining why `process`/`contains` matter (an unfiltered capture is mostly noise) and tying filter use to the volume behavior. It goes beyond the schema's bare field descriptions without duplicating them.

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?

Opens with a specific verb+resource ('Capture the iOS device's live system log...') and states the scope (a few seconds of live capture). Explicitly distinguishes itself from ios_safari_console_logs, so an agent can tell them apart without opening schemas.

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?

Names the alternative (ios_safari_console_logs) and the condition ('for a web page'), and says when NOT to use this tool. Adds timing guidance ('Run the action you want to debug WHILE the capture is running') and a prerequisite ('No automation session required'), leaving no inference to the agent.

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