conceptio_connectors_send_all

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

Annotations already declare the write/non-idempotent/open-world profile, and the description adds a genuinely new behavioral fact not in structured data: a paid-licence prerequisite with no free-trial fallback. It does not disclose duplicate-creation risk (idempotentHint=false) or partial-failure behavior on large batches, keeping it below 5.

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 short sentences, zero waste, with the core action front-loaded and the eligibility constraint immediately after. Every clause 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?

For a simple two-parameter tool with no output schema, the essentials (what it does, who can use it) are covered. But a bulk mutation accepting up to 500 IDs should say something about duplicate handling or partial-save outcomes, which is exactly the gap left by idempotentHint=false and destructiveHint=false.

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 coverage is 100%, so doc_ids range (1-500) and the single-value 'zotero' enum are already fully documented. The description's 'Bulk-save' and 'to Zotero' merely restate what the schema declares, adding no syntax, ordering, or ID-provenance detail. Baseline 3 applies.

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?

Specific verb+resource+destination: 'Bulk-save selected documents to Zotero.' The word 'Bulk' implicitly distinguishes it from the sibling conceptio_connectors_send, but the sibling is never named, so the agent must infer the single-vs-many split.

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 gives a hard gating condition ('Pro, institutional, or licensed access is required; no free trial path'), which is useful eligibility context. However, it never says when to choose this over conceptio_connectors_send, nor what to do when access is absent — usage is only implied by the word 'Bulk'.

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