wafeq_manual_journals_destroy

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

The annotations already set destructiveHint=true and readOnlyHint=false, but the description adds meaningful behavioral context by stating 'Permanently removes the record' and exposing the raw DELETE endpoint. This goes beyond the boolean hints and properly warns an agent that the deletion is irreversible.

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 short and front-loaded with the destructive warning and endpoint, but it repeats the same idea several times: 'deletes', 'Delete manual journal', 'Endpoint for deleting', and 'Permanently removes the record.' The core message is clear, but the redundancy could be trimmed.

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 destructive operation with one required parameter, the description provides the essential context: the resource, the HTTP method, the endpoint pattern, and irreversibility. The idempotency behavior is covered by the schema, and no output schema exists, so nothing critical is missing.

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 description does not directly explain the 'id' parameter, though the endpoint path '/manual-journals/{id}/' makes its purpose clear. The 'idempotency_key' parameter is well documented in the schema, including its header mapping and automatic UUID generation, so the description does not need to compensate for that parameter.

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 states a specific action ('Delete manual journal') on a specific resource ('Manual Journals') and reinforces it with the HTTP endpoint 'DELETE /manual-journals/{id}/'. It also uses the explicit '🔴 DESTRUCTIVE' warning and 'Permanently removes the record,' making the destructive intent unmistakable and distinct from the sibling retrieve/update tools.

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 clearly frames the tool's context: it is for deleting an existing manual journal and only requires the journal's id. It does not explicitly name alternatives or when not to use it, but the destructive framing and endpoint make the intended use unambiguous.

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