delete_mural

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

With no annotations provided, the description carries the full burden of disclosing behavior. It simply states 'Delete a mural' without noting that deletion is likely permanent, that it may cascade to child widgets, or that it may require special permissions. This is a significant gap for a destructive operation.

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, using just two sentences. It front-loads the action and includes only the essential parameter explanation. No words are wasted.

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 having an output schema, the description does not explain what the tool returns (e.g., success status, error codes) or describe side effects such as cascading deletion of widgets. This is a destructive operation, and the description provides no additional context beyond the act of deleting.

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 schema has 0% description coverage for parameters, and the description only adds 'mural_id: The mural ID to delete.' This clarifies the parameter's purpose but does not add format, source, or constraints beyond what the schema's type already implies. It is minimal but not worthless.

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 'Delete a mural' with a clear verb and resource. This distinguishes it from sibling tools like get_mural, update_mural, and create_mural, which share the same resource but different actions.

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, permissions, or situations where deletion might be inappropriate (e.g., if the mural is shared or contains important data).

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