delete_source

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

With no annotations provided, the description should disclose behavioral traits such as destructiveness, permission requirements, or side effects. It only states 'Delete a source' and 'Returns: Success message', which is insufficient for a mutation tool. The agent cannot infer reversibility, dependencies, or error behavior.

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 with no redundant words. It front-loads the core action in the first sentence and lists parameters and return in a clean format. Every sentence serves a clear purpose, making it efficient for an AI agent to parse quickly.

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?

Despite the tool's simplicity, the description lacks completeness. It omits details about return value format (only 'Success message'), error conditions, and required permissions. The absence of annotations and output schema leaves gaps for the agent to understand the full behavior.

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?

The description restates the parameter name and type ('source_id: Source ID') without adding meaningful context beyond the input schema. It does not explain what a source ID is, how to obtain it, or any constraints. The schema description coverage is 0%, and the description fails to compensate.

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', leaving no ambiguity about the tool's purpose. It is specific and directly corresponds to the tool name, distinguishing it from sibling tools that operate on other resources.

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 no guidance on when to use this tool versus alternatives. It does not mention prerequisites, conditions, or when not to use it. The only implied usage is deleting a source, but there is no explicit differentiation from other delete tools.

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