Remove an Author by ID from Django admin MCP. Use it to delete author records when managing content or cleaning data.
Delete a Author by ID
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | The ID of the Author to delete |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full disclosure burden for a destructive, irreversible operation. It says nothing about permanence, required permissions, cascading effects on related records, or what happens if the ID does not exist. The only behavioral signal is the word 'Delete' itself.
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?
One short, front-loaded sentence with no wasted words. Only minor grammatical awkwardness ('a Author') keeps it from being fully polished.
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 trivial one-parameter tool with no output schema and no annotations, the description is minimally adequate. It omits any note on irreversibility or failure behavior, which for a delete operation would be genuinely useful context.
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 single parameter has 100% schema description coverage ('The ID of the Author to delete'), so the schema does the heavy lifting. The description adds no format, type, or example detail beyond what the schema already states, making the baseline 3 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 names a specific verb (Delete) and resource (Author) plus the lookup key (ID), so the agent knows exactly what the tool does. It does not distinguish itself from siblings like update_author or delete_article, but the verb+resource pairing is unambiguous within the author family.
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 update_author or delete_article, no prerequisites, and no exclusions. The agent must infer usage entirely from the tool name.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.