modx_delete_media_source

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

No annotations are supplied, so the description carries the full behavioral burden, yet it only implies mutation through the word "Delete." It says nothing about whether deletion is permanent, what happens to files or resource references tied to the source, required permissions, or failure behavior for an unknown id.

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?

A single short sentence with the operation front-loaded and no wasted wording. Its brevity is clean, though it comes at the cost of the missing detail noted elsewhere.

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 destructive mutation tool with no annotations and no output schema, the definition should at minimum describe consequences and the identifier's origin. Neither is present, so an agent cannot confidently call it in a safe manner.

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 0% for the single parameter, and the description only restates it as "id" without saying it is the numeric media source identifier or how to obtain one. With one parameter the baseline would be 4 only if the schema were self-explanatory, which it is not.

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?

States a specific verb and resource ("Delete a media source") plus the lookup key ("by id"), so the agent knows exactly what the tool does. It does not distinguish itself from nearby siblings such as modx_delete_media_file, modx_delete_media_folder, or modx_delete_element, which an agent could plausibly confuse with it.

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 on when to use this versus the file/folder deletion siblings, no prerequisite check (e.g., confirm the source exists via modx_list_media_sources), and no warning about irreversibility. The agent is left to infer all usage conditions.

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