akb_unpublish

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It explains the destructive effect (removing a public share) and the two modes of operation, but does not mention permissions, reversibility, or side effects like whether the resource remains visible elsewhere. Some transparency is present, but gaps remain.

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 sentence that packs all necessary information without any fluff. Every word serves a purpose: action, target, parameter guidance. Optimal conciseness.

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?

While the description covers the core functionality for a simple deletion tool, it lacks mention of return values, error conditions, or prerequisites. With no output schema and no annotations, more context (e.g., relationship to akb_publish, behavior when both parameters are provided) would improve completeness.

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 already provides 100% coverage with descriptions for both parameters. The description adds semantic value by explaining the functional difference between the two parameters (single deletion vs. bulk deletion) and implicitly indicates they are alternatives. This goes beyond the schema's basic descriptions.

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 clearly states the tool removes a public share, distinguishing between single publication deletion (by slug) and all publications for a resource (by uri). This is a specific verb+resource combination that differentiates it from siblings like akb_publish and akb_publications.

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 explicitly provides usage guidance: 'Pass `slug` to delete a single publication, or `uri` to delete all publications for that resource.' This tells the agent exactly when and how to use each parameter, making it highly actionable.

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