opensolr_delete_documents

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

No annotations are present, so the description carries the behavioral disclosure burden. It does reveal that deletion can be performed by IDs or a raw query, and gives concrete query examples. However, it omits important traits such as irreversibility, commit behavior, permission needs, and the effect of supplying both `ids` and `query`.

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, well-structured sentence front-loads the action and immediately provides selection modes with examples. Every word earns its place; there is no redundant or filler content.

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?

The output schema likely covers return values, so the description need not detail those. For a destructive operation with no annotations, a note on permanence or at least one expected ID/query requirement would improve completeness. Otherwise the core deletion modes are adequately captured for a tool of this complexity.

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 0%, so the description must compensate. It adds useful meaning to `ids` by clarifying 'Solr ids or your original ids' and gives raw query examples for `query`. Yet it does not describe the required `index` parameter nor whether `ids` and `query` are mutually exclusive or can be combined.

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 a specific action ('Delete documents') and the two selection modes (IDs or raw query). This clearly distinguishes it from sibling tools like opensolr_search, opensolr_add_documentss, and opensolr_list_indexes, which serve different purposes.

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?

No guidance is provided on when to choose this tool over alternatives, nor any exclusions or prerequisites. The intended usage is implied by the name and description, but no explicit when/when-not context exists.

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