Edit or delete a private intel feed item

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

Annotations already declare destructiveHint=true, idempotentHint=false and readOnlyHint=false, so the safety profile is covered. The description adds the real value of the intel:write authorization requirement, but omits the delete preview/human-approval flow that the confirm parameter implies, and says nothing about reversibility.

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?

Two tight sentences with zero filler; the action pair is front-loaded and the permission requirement follows immediately.

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 destructive mutation with five parameters and no output schema, the definition covers the action and permission but omits the two-step delete flow (preview then confirm) and the merge/replace semantics of the item payload, both of which live only in the schema.

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 only 40% (action, feed_id, item_id undocumented), but those undocumented parameters are a self-describing enum and two UUIDs with explicit patterns. The description adds nothing parameter-specific, though the remaining gap is small because the schema is structurally rich.

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?

"Edits or deletes one item in a private intelligence feed" gives a specific verb pair and resource, and "one item" implicitly separates it from the plural/bulk siblings (upsert_customer_intel_items, manage_customer_intel_feed). It never names those siblings explicitly, so the differentiation is left to inference.

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 only usage guidance is the prerequisite "Requires intel:write." There is no statement of when to pick this single-item tool over upsert_customer_intel_items or manage_customer_intel_feed, nor when update vs delete applies beyond the enum in the schema.

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