disable_telemetry

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

With no annotations provided, the description carries the full burden. It discloses immediate effect ('Takes effect immediately'), the irreversible nature via this tool, and the precise method to re-enable. This exceeds typical transparency for a simple toggle.

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?

Three tightly packed sentences: the primary function, explicit triggers, and the critical limitation. All sentences earn their place, and the most important information is front-loaded.

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 opt-out tool, the description covers action, timing, triggers, and limitations. The output schema exists (though not detailed here), but for this operation the description is sufficient for an agent to invoke correctly.

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 single parameter 'user_prompt' is optional with a default and has 0% schema coverage in the description. The description does not explain its purpose or whether agents should populate it. Although the tool works without it, the lack of any guidance leaves ambiguity about how to use it.

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 states a specific action ('Turn OFF collection') against a clear resource (prompts, code, screenshots, scene data). It is unambiguous and distinct from the sibling tools, none of which deal with telemetry control.

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?

Explicitly states when to use: 'whenever the user asks to stop data collection, opt out of telemetry, or stop sharing their data.' Also clarifies the tool's one-way nature and directs the user to the manual re-enable path, giving agents complete usage context.

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