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

The annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is covered. The description adds meaningful behavioral context beyond the annotations: all image delivery using the subdomain will be stopped. It does not mention permissions or whether the deletion is reversible, but the key operational consequence is disclosed.

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 two concise sentences with no filler. It front-loads the action and immediately follows with the most important consequence, making it easy for an agent to parse.

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 simple one-parameter deletion tool with a full output schema and safety annotations, the description covers the essential action and side effect. It could be slightly stronger by noting permission requirements or confirming irreversible behavior, but it is largely complete for agent decision-making.

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 input schema fully documents the single required parameter, including where to find the image source ID on the Gumlet dashboard or via the list source API. Schema description coverage is 100%, so the baseline is 3; the description adds no parameter-specific meaning beyond what the schema already provides.

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 and resource: it removes an image source. It also clarifies the scope by noting that image delivery through the source's subdomain will stop, which helps distinguish it from sibling delete tools such as delete_asset or delete_workspace. It does not explicitly name siblings, but the purpose is clear.

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?

Usage is implied: use this to delete an image source. However, the description gives no explicit guidance on when to prefer this over alternatives like update_image_source, image_purge, or purge_image_cache, nor does it state prerequisites or when deletion should be avoided. It provides impact context but not routing guidance.

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