suppliers_bulk_delete

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

No annotations are provided, so description carries the burden. It discloses 'soft-delete' (non-permanent) and that it returns a count of deleted items and errors. However, it doesn't explain what 'soft-delete' means for later visibility/restoration, partial-success semantics (partially deleted?), or whether the operation is atomic. Given zero annotations, this is a moderate gap.

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?

Two sentences, zero waste. Front-loaded with the core purpose, followed by a useful return-value note. Every word earns its place.

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?

Tool has 2 params (100% schema coverage) and no output schema. Description explains it returns count and errors, which is useful. For a mutation tool with no annotations, it could disclose more about soft-delete implications (recovery, filtering in list endpoints) and error-handling behavior. Competent but not rich.

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%, with both ids and companyId described in schema. The description adds 'Returns count of deleted items and errors' context but not parameter-specific meaning. Baseline 3 is appropriate since schema fully documents parameters.

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?

Uses specific verb 'soft-delete' with resource 'multiple suppliers in a single request'. Clearly distinguishes from suppliers_delete (single). The word 'soft-delete' adds precision indicating non-destructive behavior, differentiating from a hard delete concept. Description is clear but doesn't explicitly contrast with siblings in the text itself.

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?

States it handles multiple suppliers in a single request, implying use for batch deletions. But no explicit guidance on when to choose this vs suppliers_delete, nor any batch-limit context (maxItems 100 in schema helps). No exclusions or alternative tool named. Adequate but minimal.

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