resetToolTelemetry

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

No annotations are provided, so the description must fully disclose behavioral traits. It states 'reset' but does not mention that this action is destructive (erases historical telemetry), whether it requires special permissions, or any side effects on ongoing metrics. The minimal description leaves significant behavioral uncertainty.

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 sentence that is concise and to the point. Every word contributes: 'Reset' is the action, 'rolling performance telemetry' is the resource, and 'for one tool or all tools' clarifies the scope. No wasted text.

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 tool with one optional parameter, the description covers the core action and scope. However, it lacks usage guidance and behavioral transparency, leaving gaps in what the agent needs to know for correct invocation. The presence of an output schema partly compensates for missing return value details.

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 schema has 0% description coverage and defines one parameter 'tool_name' with anyOf string/null. The description adds critical meaning by implying that when 'tool_name' is null (default), it resets all tools, and when provided as a string, it resets that specific tool. This goes beyond the schema alone, though it could be more explicit about the parameter behavior.

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 verb 'reset' and the resource 'rolling performance telemetry', and explicitly indicates the scope ('for one tool or all tools'). This differentiates it from the sibling tool 'getToolTelemetry' which retrieves telemetry.

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?

The description implies usage for resetting telemetry, but provides no explicit guidance on when to use this tool over alternatives, nor any conditions or exclusions. The sibling 'getToolTelemetry' suggests when to get vs reset, but the description itself lacks direct guidance.

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