get_status

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

With no annotations, the description carries the burden, and it does convey that this is a state-reporting read exposing counters and safety settings. It omits whether the call is side-effect free, whether it is cached/cheap, or any auth/latency context an agent would want before polling it.

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 compact clause with zero padding, front-loading the most important item (bridge connectivity). It is a noun phrase rather than a sentence, so it reads as a return-value stub rather than a self-contained definition.

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?

The output schema already documents return values, so the description's field enumeration largely duplicates structured data instead of adding the guidance an agent needs (when to poll, how it relates to session/traffic tools). For a zero-param diagnostic getter the bar is low, but the description still stops short of full context.

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 tool takes zero parameters and the schema is empty, so there is no parameter semantics to explain; baseline 4 applies. The field list in the description maps to returned data rather than inputs, and adds no confusion.

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 enumerates exactly what the tool reports (bridge connectivity, Charles version, recording state, counters, safety settings), so the resource is unmistakable even though there's no explicit verb. It does not differentiate from siblings such as get_session_summary, which could plausibly overlap in reporting 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 statement of when to call this versus get_session_summary or watch_requests, and no exclusions or prerequisites. The agent must infer that this is a health/diagnostic snapshot call.

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