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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so the safety posture is largely pre-supplied. The description adds one meaningful piece of context beyond them: "Permanently" signals a hard, irreversible delete rather than an archive or soft delete. It says nothing about cascading effects on related records or authorization requirements.

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?

One short sentence, front-loaded with the verb and the irreversible qualifier, with no redundant or filler wording.

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 single-parameter delete with rich annotations and no output schema, the definition is minimally sufficient. It is missing what an agent would want before a destructive call: whether dependent warehouse job records are removed, what failure looks like for an unknown ID, or any authorization requirement.

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?

With a single required parameter at 100% schema coverage, the schema baseline applies. The description only restates that the identifier is an ID ("by ID"), adding no format, source, or lookup guidance beyond the schema's own "ID." field description.

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 names a specific verb ("delete") and resource ("Warehouse Job") with a stated scope ("one ... by ID"), and the qualifier "Permanently" separates it from a soft-delete or update. In a sibling set crowded with delete_* variants, the resource noun does the differentiation work, but it never explicitly contrasts with update_warehouse_job or get_warehouse_job.

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?

There is no when-to-use or when-not-to-use guidance, no mention of prerequisites (ownership/permissions), and no pointer to update_warehouse_job for modification instead of removal. An agent must infer all routing decisions from the tool name alone.

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