Delete Productivity Log

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

The description adds behavioral context beyond annotations: it confirms destructiveness ('cannot be undone,' 'permanently removes'), echoes the endpoint path, and indicates required parameters. The annotations already set destructiveHint=true, so the description aligns and adds detail about irreversibility and API structure.

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 contains redundancy: 'This cannot be undone' is stated twice. It is about 3 sentences, but could be more concise by merging the two permanence statements. It includes helpful context like API endpoint but has minor repetition.

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 no output schema, the description covers the purpose, irreversibility, parameters, and technical reference (endpoint). It is sufficiently complete to allow an agent to understand the tool's behavior and requirements.

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 already covers both parameters with clear descriptions (URL path parameters for project_id and id). The description restates that they are required and shows them in the endpoint URL, but adds minimal new semantic value beyond what the schema provides.

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 it deletes a single productivity log permanently. It specifies the resource and action precisely, distinguishing it from other delete tools like delete_productivity_log's siblings (e.g., delete_accident_log, delete_call_log).

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?

It explains when to use the tool (to delete a productivity log) and notes that the action cannot be undone. However, it does not provide guidance on when not to use it or suggest alternatives such as bulk delete or archive options.

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