remove_source

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

The description explicitly says 'Delete', so the destructive nature is clear. However, with no annotations, the description carries the full burden and does not disclose permanence, side effects on other source-related data, or what happens if the tag does not exist.

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, front-loaded sentence with no filler; it is easy to parse. The brevity is effective but comes at the cost of omitting essential parameter context.

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?

For a tool with three parameters, two of which are required, and no annotation support, this description is too thin for an agent to invoke the tool correctly without guessing. The output schema covers return values, but the roles of 'path' and 'out' and the relationship between path and tag remain unexplained.

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 gives a minimal role to 'tag' as the identifier, but it does not explain the required 'path' parameter or the optional 'out' parameter. Schema description coverage is 0%, and the schema itself only provides titles and types, so the description does not compensate for the missing parameter semantics.

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 states a specific verb ('Delete') and resource ('source') and identifies the tag as the selection mechanism. It clearly functions as the deletion counterpart to siblings like add_source and list_sources, though it does not define what a 'source' is or how it relates to the required 'path'.

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?

There is no guidance about when to use this tool versus alternatives such as add_source, list_sources, or import_references. No prerequisites, conditions, or exclusions are mentioned; only the basic action is stated.

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