delete_metric_data_points

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. While it names the target resource, it does not disclose whether deletion is permanent, whether all data points at the timestamp are removed, or any side effects. For a destructive operation, this is a significant gap.

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, front-loaded sentence of 11 words. Every word earns its place, and there is no redundancy or filler.

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 two documented parameters, the core purpose is clear. However, with no annotation and no output schema, the description should address behavior when no matching data points exist, permanence, and the scope of deletion (all points at timestamp vs one). These gaps leave the description only minimally complete.

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 100%, and the description aligns with the timestamp parameter. However, it adds no new meaning beyond what the schema already provides, such as clarifying whether the operation deletes all data points at that timestamp or just one.

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 uses the specific verb 'Delete' with a clear resource ('data points from a DAKboard metric') and a precise scope ('at a specific timestamp'). It clearly differentiates from sibling tools like delete_metric (which deletes the entire metric) and create_metric_data_points.

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 removing specific data points rather than the whole metric, but it does not explicitly state when to use this tool vs alternatives. Sibling names like delete_metric provide context, but the description relies on inference rather than explicit guidance.

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