backup_dataset

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

With no annotations, the description carries the full burden and does so thoroughly: it discloses the write location (Fuseki's backups directory), the async nature (runs in background, returns a task id), and the rationale for its read-tool classification (copies data out, stays available under read-only servers). That read-only justification is exactly the kind of trait annotations would normally supply.

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?

Front-loads purpose, then placement/async behavior, then the safety rationale, then the read-tool justification. Every sentence contributes a distinct operational fact; there is no filler despite the multi-paragraph length.

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?

No output schema exists, and the description compensates by explaining what is returned (a task id) and how to consume it (poll with task_status). Combined with destination and safety context, an agent has everything needed to invoke this correctly.

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% and the single 'dataset' parameter already documents its defaulting behavior, so the description needs to add nothing and doesn't. Baseline 3 applies since the schema does all the parameter work.

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?

Opens with a precise verb+resource: 'Start a server-side backup of a dataset.' The scope word 'server-side' immediately distinguishes it from anything client-side or export-oriented, and the sibling set (delete_dataset, drop_graph, compact_dataset) all deal with different lifecycle actions.

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?

Gives explicit when-to-use ('Do this before anything destructive') and names the exact risks it protects against ('no undo for drop_graph or delete_dataset'), which are real siblings. It also hands off the follow-up step by naming task_status as the polling mechanism.

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