spoolman_trigger_backup

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

With no annotations, the description must disclose side effects. It does state that the tool triggers a backup (a side effect) and returns the backup file path. However, it does not mention potential effects like whether it overwrites existing backups, whether it blocks, or any permission requirements. This is a moderate level of disclosure for a simple trigger.

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?

The description is two concise sentences that front-load the core action and include the return value. Every word earns its place, with no redundancy or fluff.

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?

Given the tool's simplicity (zero parameters, no output schema), the description sufficiently covers its behavior and return value. The 'SQLite only' constraint is a valuable addition. No further details are needed for an agent to invoke this tool correctly in most scenarios.

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?

The tool has zero parameters, and the description accurately adds no parameter-specific meaning since there are none. Baseline for 0 parameters is 4, and the 'SQLite only' qualifier provides useful context beyond the empty schema.

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 clearly states the action (trigger a database backup), the resource (the Spoolman instance), and a key qualifying constraint (SQLite only). It is specific and distinguishes itself from all sibling tools, none of which are backup-related.

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 implies the tool should be used when a database backup is needed, but it does not explicitly state when to use it over alternatives or when not to use it. Since there are no sibling backup tools, the usage context is clear but not formally stated.

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