Delete source

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

With no annotations, the description carries the full burden. It discloses the permanent, destructive nature ('Permanently remove'), the risk ('High-impact'), and the confirmation requirement. This goes beyond the schema by adding crucial safety context, though it doesn't mention side effects like removal from all scenes.

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 short sentences deliver all essential information in a front-loaded manner. Every word earns its place: 'Permanently remove a source. High-impact: requires confirmation.'

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?

The description is sufficient for a simple delete tool, but it lacks explicit differentiation from remove_source_from_scene and does not clarify how confirmation is provided (e.g., setting confirm=true). The output schema covers return values, but the description could be more complete about the tool's scope and execution requirements.

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%, and the description does not explain either parameter. It only hints at confirmation without naming the 'confirm' parameter or its required value (true) to execute. The 'source_name' parameter is obvious, but the description adds minimal semantic value over 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 tool's function: 'Permanently remove a source.' The verb 'remove' combined with 'permanently' distinguishes it from sibling tools like hide_source or remove_source_from_scene, making the purpose unambiguous.

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 phrase 'High-impact: requires confirmation' provides clear context that this is a destructive action needing user confirmation. It does not explicitly name alternatives or exclusion criteria, which prevents a 5, but the cautionary context is helpful.

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