source_delete

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

With no annotations provided, the description carries the full burden. It discloses irreversibility and the confirm requirement, which are critical. However, it does not discuss potential side effects (e.g., cascading deletions) or permission requirements, leaving gaps in behavioral transparency.

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 extremely concise: five lines including the signature. It front-loads the key warning about irreversibility and the confirm requirement. Every sentence serves a purpose with no wasted words.

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?

Given the tool's simplicity (delete source) and the existence of an output schema, the description covers essential aspects: irreversibility, single vs bulk, and confirmation. It lacks potential error scenarios but is sufficient for a deletion tool.

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 0%, so the description must fully explain parameters. It does so by clarifying that source_id is for single deletion, source_ids for bulk, and confirm must be True. This adds meaning beyond the schema's type definitions.

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 clearly states 'Delete source(s) permanently' with emphasis on irreversibility. This is a specific verb-resource pair that distinguishes the tool from sibling tools like source_add or source_describe.

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 explicitly requires confirm=True, implying user approval is needed before deletion. It does not explicitly state when to use this tool over alternatives, but the context of deletion is clear and no sibling tool offers deletion for sources.

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