Delete Dumpster Log

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

Annotations already declare destructiveHint=true and readOnlyHint=false, but the description adds crucial behavioral context: 'Permanently removes the dumpster log. This cannot be undone, and a repeat call returns 404.' It also discloses error semantics (401, 403, 404) with common causes, which is very useful for an agent anticipating failure modes. No contradiction with 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?

The description is dense and front-loaded with the core action, then usage guidance, then parameter details, then API context. It is a bit long and includes some redundancy (e.g., 'Required parameters: project_id, id' repeats the schema), but every additional sentence contributes useful detail — no 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 delete tool with no output schema, the description covers the important operational aspects: permanent deletion, repeat-call behavior, and error statuses. It does not explicitly describe the success return (e.g., 204 No Content), which would be a minor gap, but overall it gives an agent enough to call the tool safely and interpret failures.

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%, so the baseline is 3. The description goes beyond by explaining that project_id defaults to the configured company/project when omitted and that id must identify an existing record resolved via the list tool. This adds real operational meaning to the schema fields.

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 opens with 'Delete single Dumpster Log' — a specific verb and resource. The word 'single' clearly distinguishes this from sibling tools like list_dumpster_logs, create_dumpster_log, and show_dumpster_logs. The purpose is unambiguous and action-oriented.

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?

Explicitly instructs to 'Confirm the target id with the matching show or list tool before calling' and to 'resolve it with the matching list tool first.' This directly addresses when to use associated lookup tools and provides guidance on parameter resolution, going well beyond a generic description.

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