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

With no annotations, the description carries the full behavioral disclosure burden. It communicates that this is a read-only reporting operation (no mutation implied) and specifies the two pieces of information returned (running state, buffered flow count). However, it does not mention side effects, permissions, or whether the status refers to a session started by ios_traffic_start. This is adequate but minimal.

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 sentence that front-loads the primary action ('Report') and concisely covers the two key outputs. No extra words, no repetition of schema details, and no vague filler.

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 simple status-check tool with one parameter and no output schema, the description tells the agent what the tool returns (TLS inspection state and buffered flow count). It does not describe the output format or units, but this is a minor gap for a low-complexity query. The essential information needed to invoke it correctly is present.

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?

The schema covers 100% of parameters (udid) with a clear description, so the baseline is 3. The tool description adds no additional semantic context about the parameter beyond what the schema already provides. Since schema description coverage is high, the description does not need to compensate.

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 uses the specific verb 'Report' and names the exact resource: TLS inspection status plus buffered flow count. It clearly distinguishes itself from sibling tools like android_traffic_status (platform-specific) and ios_traffic_flows (which reports flows rather than status). An agent can identify this tool's purpose without inspecting the schema.

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 context of platform-specific siblings (android_traffic_status, ios_traffic_flows) makes the usage somewhat implicit: it is for iOS device traffic inspection status. However, the description does not explicitly state when to use this tool versus alternatives, such as after starting traffic capture or when needing only the buffered flow count. There is no explicit exclusion or alternative naming.

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