device_data_push

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

No annotations are provided, so the description carries the full burden, and it is exceptionally transparent. It discloses opt-in default behavior, declaration validation, desensitization, AES-256-GCM encryption, WAL persistence across disconnects, cursor resume with no retransmission of acked segments, audit trail, metering into worklog, and the raw-data-never-leaves-device guarantee.

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 dense arrow-flow sentence with no filler, and the most important constraints are front-loaded (device gate → declaration validation). However, unexplained abbreviations like 'G11', 'WAL', and 'ack' plus the run-on structure reduce quick readability.

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 security-sensitive mutation tool with no annotations and no output schema, it is highly complete: validation, encryption, persistence, retry behavior, audit, metering, and data residency are all covered. It does not explicitly state return/error semantics or optional-destination handling, but those are minor compared to the rich pipeline context provided.

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 100%, so the baseline is 3. The input schema already explains payload, category, identity, and destination; the description reinforces the pipeline (e.g., encryption before enqueue) but adds little per-parameter semantic meaning beyond the schema.

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 device-data uplink pipeline ('数据上行通道') and enumerates the processing chain (gate, declaration validation, desensitization, AES-256-GCM encryption, enqueue). It is reasonably distinguishable from generic siblings like data_push and device_data_query via the device/opt-in/raw-data framing, though 'G11' is unexplained and the tool's direct 'push to destination' verb is only implied.

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?

It gives clear usage conditions: data is only uploaded when opted in, must pass the device gate and collection-declaration validation, and destination is checked against the declaration. It does not explicitly name alternatives such as data_push or router_session_push, so cross-tool routing guidance is implied rather than explicit.

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