telemetry_unsubscribe

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

No annotations are provided, so the description must disclose side effects and behavior. It does not mention what happens to collected data, whether stopping is immediate, or any required permissions. For a mutation tool, this is insufficient.

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 very short but lacks important details. It is not a model of conciseness because it omits critical information that would help the agent use the tool correctly.

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?

While an output schema exists (so return values may be documented), the description fails to mention success/failure indicators, prerequisites (e.g., must have an active subscription), or error conditions. The tool is incomplete given its mutation nature.

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 0%, so the description must compensate. The 'device' parameter is described only as 'Name of the device to stop collecting from', which adds no meaning beyond the schema. No format, validation, or source hints are given.

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 the action ('Stop a telemetry subscription') and the resource ('for a device'). It implicitly distinguishes from sibling tools like telemetry_subscribe (the opposite) and telemetry_list_subscriptions (listing). However, it does not explicitly differentiate itself or mention that it requires an existing subscription.

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?

No guidance is provided on when to use this tool versus alternatives (e.g., telemetry_list_subscriptions to find subscriptions first). The description only says 'Stop...' without context about prerequisites or typical workflow.

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