Delete Daily Construction Report Log

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

Annotations already indicate destructiveHint=true and readOnlyHint=false. The description expands by adding 'This cannot be undone' and 'Permanently removes', reinforcing the irreversible nature. It also specifies the operation is for a single record, which annotations do not convey.

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 repetition ('This cannot be undone' appears twice) and could be more concise. The first two sentences are somewhat redundant. Otherwise, it is structured logically with purpose, usage, and endpoint details.

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 tool with two parameters and no output schema, the description covers purpose, irreversibility, and required parameters. It does not mention response codes or permissions, but the destructive hint and simplicity make it adequately 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 coverage is 100% with descriptions for both parameters. The description only reiterates that project_id and id are required, adding no new meaning. The endpoint path in the description provides context but does not deepen parameter understanding.

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 tool deletes a single Daily Construction Report Log. It specifies 'permanently delete' and 'cannot be undone', distinguishing it from sibling tools like create, update, show, and list. The name and title also align.

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 explicitly says 'Use this to permanently delete the specified Daily Log records.' It also lists required parameters. While it does not provide exclusions or alternatives, the context of being the only delete tool for this log type makes the usage clear.

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