delete_article

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and idempotentHint=true, and the description offers no additional behavioral context such as irreversibility, cascade effects, permission requirements, or response behavior. The text merely restates the action rather than enriching it beyond the 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?

One short sentence contains no filler and is appropriately front-loaded with the action. It earns its place but could have added useful caveats without significantly reducing conciseness.

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 one-parameter delete operation, the annotation set covers destructive and idempotent behavior, making the short description minimally adequate. It lacks explicit notes on irreversibility or side effects, but given the strong schema and annotation coverage, the gaps are modest.

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% and the single 'id' parameter is documented as 'Article ID to delete'. The description adds no further semantic detail beyond the schema, which is acceptable at the baseline for fully covered schemas.

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?

States a specific action ('Delete') and a clear resource ('Help Center article'), leaving no ambiguity about what the tool does. It is also distinguishable from sibling tools such as delete_ticket, create_article, update_article, and get_article by naming the article resource and the deletion verb.

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 gives no guidance on when to choose this tool over alternatives or any exclusions or prerequisites. An agent must infer from the tool name and sibling list that delete_article is for removing articles rather than tickets or other Help Center entities.

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