Delete metrics stream

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

Annotations already indicate destructiveHint: true and idempotentHint: true. The description adds minimal context beyond stating the DELETE call. It does not disclose what happens if the owner ID does not exist or any cascading effects, providing little extra value over the annotations.

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?

Two concise sentences: first states purpose, second references the API call. No fluff, front-loaded, and efficiently conveys the essential information.

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 delete operation with one parameter and no output schema, the description is adequate but lacks details on error handling, success response, or idempotency behavior (though annotations cover idempotentHint). It is minimally complete but could be more thorough.

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 input schema has full coverage (1 parameter), but the schema description for ownerId incorrectly states 'return metrics stream information', which contradicts the delete action. The tool description clarifies the parameter's purpose ('for the specified workspace') but does not add meaning beyond the schema. The baseline of 3 is reduced due to the misleading schema description.

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 'Delete', the resource 'metrics stream', and specifies 'for the specified workspace'. It also provides the API endpoint, distinguishing it from sibling tools like render_get_owner_metrics_stream and render_upsert_owner_metrics_stream.

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 explicit guidance is provided on when to use this tool vs alternatives, such as conditions for deletion, prerequisites, or when not to use. Users must infer usage from the tool name and description alone.

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