da_admin_delete_source

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

The description mentions that the tool can delete html or json files, but lacks important behavioral details such as whether the deletion is permanent, if it triggers cascading effects, or what permissions are required. No annotations are present to compensate.

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 that is front-loaded with the verb and resource. It is concise, though it sacrifices completeness for brevity. Every word earns its place.

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 no output schema or annotations, the description should provide more context about the tool's behavior (e.g., return value, success indicators, or data permanence). For a delete operation with four required parameters, the description is too sparse to fully guide the agent.

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 100%, so the schema already documents all parameters. The description adds minimal value beyond stating the file types (html or json), which overlaps with the 'ext' parameter description. Baseline score of 3 is appropriate.

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 action ('Delete') and the resource ('source content'), specifying the file types (html or json). This distinguishes it from sibling tools like da_admin_list_sources (list) and da_admin_create_source (create).

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 the tool is used to delete source content, but does not explicitly state when to use it versus alternatives (e.g., da_admin_list_sources for exploration, da_admin_create_source for creation). No 'when not to use' guidance is provided.

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