conceptio_connectors_send

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

Annotations already cover the safety profile (destructiveHint=false, idempotentHint=true, openWorldHint=true), so the description only needs to add context. 'Server-side ownership, connector trial, and failure semantics apply' gestures at entitlement and failure behavior without saying what those semantics actually are, which leaves the agent guessing about error modes for an open-world side-effecting call.

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 tight sentences with the action front-loaded and no filler. Nothing is wasted, though the brevity is arguably at the cost of the missing detail noted elsewhere.

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?

There is no output schema, so the description should say what comes back from a save versus an Obsidian handoff (confirmation, URL, item key). Instead it defers to a vague 'failure semantics apply' clause, leaving the return shape of an open-world write undefined.

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 the schema already explains connector and doc_id. The description's Zotero/Obsidian split repeats what the connector enum description already states, and the optional 'vault' parameter is never mentioned. Baseline 3 is appropriate.

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?

States a specific verb and resource ('Save one document to Zotero or open a metadata-only Obsidian handoff'), and the word 'one' implicitly separates it from the sibling conceptio_connectors_send_all. It never names that sibling explicitly, so the differentiation is inferred rather than stated.

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 dual-mode phrasing implies when each connector applies, but there is no explicit guidance on when to prefer this over conceptio_connectors_send_all, no prerequisites spelled out, and no exclusions. Usage must be inferred from the connector semantics.

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