delete_global_source

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

With no annotations provided, the description carries the full burden for behavioral disclosure. It does reveal a key trait—that it also deletes the published version—which goes beyond the bare action. However, it omits other destructive-operation traits like irreversibility, permission requirements, or cascading effects, leaving significant gaps.

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 a single sentence, front-loaded with the action verb, and contains zero filler. Every word adds value: the resource, the action, and the notable detail about the published version.

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 tool with no output schema, the description is largely complete: it states the action, the target, and an important scope detail. It does not explain error conditions or post-deletion behavior, but given the tool's simplicity, those omissions are not critical.

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 schema already fully describes the single parameter (global_source_id) with a description ('Global source ID to delete'), and the tool description adds no additional semantic meaning beyond repeating the schema. With 100% schema coverage, the baseline is 3, and no enhancement is provided.

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 uses a specific verb ('Delete') and resource ('global source') and adds a key differentiator ('and its published version'), clearly distinguishing it from sibling tools like update_global_source, get_global_source_detail, or delete_global_section.

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 implies usage (when you need to delete a global source) but provides no explicit guidance on when to use this tool versus alternatives, nor any exclusions. The mention of deleting the published version hints at scope but does not cover prerequisites or alternative actions like unpublishing.

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