app_sensor_snapshot

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

The description adds 'non-blocking', 'pushes a state request', and 'returns latest bridge push + live var read', which gives some context beyond the readOnly/idempotent annotations. Yet it does not explain timeout behavior, freshness guarantees, or what 'bridge push' exactly entails.

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 short and front-loaded with the key signal ('LIVE: non-blocking'), but the second sentence partially repeats the first and adds only moderate value. It is nearly tight, with minor redundancy.

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 read tool with rich annotations, the description covers the gist and main return content. However, it leaves the agent guessing about timeoutMs semantics, what 'bridge push' refers to, and how 'name' omitting changes behavior beyond the schema line.

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 description does not add any meaning to the parameters. The schema describes 'name' but not 'timeoutMs', leaving 50% coverage; the description does nothing to compensate, so an agent cannot tell what a timeout actually controls.

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 clearly states a live, non-blocking sensor/variable read and explicitly mentions pushing a state request and returning the latest bridge state. However, it does not distinguish itself from the sibling app_get_var or app_status, so an agent must inspect schemas to choose the right read tool.

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 use this tool versus alternatives like app_get_var or app_status. The 'LIVE' qualifier implies it is for fresh snapshots, but no exclusions or alternative conditions are stated.

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