source_delete

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

With no annotations provided, the description carries full burden and excels by disclosing critical behavioral traits: the operation is 'IRREVERSIBLE' (destructive nature), requires user approval via 'confirm=True', and permanently deletes the source. This covers safety and confirmation needs beyond basic function.

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 front-loaded with the core action and warning, followed by a structured Args section. Every sentence earns its place: the first states purpose and critical constraints, while the parameter explanations are necessary given low schema coverage.

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 high complexity (destructive, irreversible operation) and no annotations, the description is complete: it covers purpose, behavioral risks, parameter semantics, and usage context. The presence of an output schema means return values don't need explanation here.

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 0%, so the description must compensate fully. It does so by explaining both parameters: 'source_id' as 'Source UUID to delete' and 'confirm' as 'Must be True after user approval', adding essential meaning about UUID format and confirmation logic not in the schema.

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 the verb 'Delete' and resource 'source', specifying it's a permanent deletion. It distinguishes from siblings like source_describe and source_list_drive by focusing on destructive removal rather than querying or listing.

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 provides clear context with 'Requires confirm=True' and 'after user approval', indicating when to use this tool (for irreversible deletion with confirmation). However, it doesn't explicitly mention when not to use it or name alternatives like source_describe for checking before deletion.

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