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

Beyond the annotations (which already flag destructive/idempotent), the description clarifies that only the reference is removed because 'Collections store references, not copied content,' and it discloses 404 behavior for private/withdrawn collections and no-store caching. It does not state authorization/ownership requirements, but the added behavioral context is genuine.

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 purpose is front-loaded, but roughly half the text ('Owner search reads current files...', 'Publication includes only references to currently public bases...', 'Every public read checks base publication again') describes publication/search mechanics that are tangential to removing a base reference. These sentences do not earn their place in this tool's definition.

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?

Annotations cover the destructive/idempotent profile and the description adds what is destroyed and the 404 path, with no output schema needed. It is adequate, but the filler crowds out genuinely useful missing details such as permissions required to remove a reference.

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 100%, so both IDs are documented in the schema and the baseline is 3. The description adds no per-parameter meaning (no format, no origin, no constraints beyond what the schema already carries).

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 opening sentence gives a specific verb+resource+scope: 'Remove a base reference and its collection search results,' which separates it from remove_collection and remove_base_document by operating on a base reference inside a collection. It stops short of explicitly naming those siblings, so it is clear but not fully differentiated.

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 when-to-use, when-not-to-use, or alternative routing. Nothing tells the agent how this differs from remove_collection or remove_base_document in a given situation, or when removing a reference is appropriate versus unpublishing.

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