remove_data_source

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

With no annotations, the description carries full burden. It discloses refusal on references and the force option, but lacks details on permissions, reversibility, or post-removal state. The behavioral disclosure is adequate but not comprehensive.

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 sentences, front-loaded with the action, and every phrase adds value. No redundancy or unnecessary information. Highly concise and structured.

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 covers the core behavior and force option, but misses details like what constitutes a valid path, success indication, and whether the action is reversible. For a tool with no output schema and no annotations, more context is needed for full completeness.

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 should compensate. It explains 'force' partially, but 'name' and 'path' are not described beyond naming the DataSource. The meaning of 'path' is unclear, and the format of 'name' is not specified.

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 'Remove a named <DataSource>', which is a specific verb-resource pairing. It distinguishes from sibling tools like add_data_source or rename_data_source, and the context of removing a data source is 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 description explains the default refusal behavior and how to override with force=True, providing clear context for when to use the tool. Though it doesn't explicitly state alternatives, the name and context imply this is the only removal tool for data sources.

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