akb_unpublish

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

No annotations present, but description discloses the return format ({deleted: N}) and the nature of the operation (removal). Could mention idempotency or error handling for missing slugs/uris, but is adequate.

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?

Three concise sentences, front-loaded with purpose, no fluff. Every sentence adds useful information.

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?

Given zero annotations and no output schema, the description covers both parameters, return value, and an important edge case. It is self-contained and sufficient for confident use.

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?

Adds significant value beyond schema descriptions: explains the semantic difference between slug and uri, and clarifies that table_query publications lack URI so must use slug.

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 'Remove publication(s)' and distinguishes between removing one by slug or all by URI, with a specific edge case for table_query publications. It contrasts with 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?

Explicitly advises when to use slug vs uri, and mentions the handy use case for re-publishing. Provides enough context to choose correctly.

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