✓ SAFE: Create consistent SQLite backup via online backup API. Includes committed WAL data. Auto-timestamps if no path specified.

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

With no annotations, the description carries full burden. It mentions safety, WAL inclusion, and auto-timestamps, but omits critical details such as where the backup is stored, file overwrite behavior, return value, and required permissions or database state.

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 a single sentence with no wasted words, front-loaded with 'SAFE'. However, it repeats the title verbatim, and could benefit from structuring key points separately.

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 2 optional parameters, no output schema, and many sibling tools, the description lacks completeness. It does not explain the return value, side effects, or how 'source_database_name' affects the backup, leaving gaps for an AI agent.

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 0%, so description must compensate. It explains 'auto-timestamps if no path specified' for backup_path, but does not describe the 'source_database_name' parameter at all, leaving half of the parameters semantically undocumented.

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?

Tautological: description restates name/title.

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 usage for creating consistent backups but does not explicitly contrast with alternatives like 'export_csv' or 'database_info'. No exclusions or when-not-to-use guidance is provided.

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