sync_database

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

Discloses idempotency, which is useful. No annotations provided, so the description carries the burden. Lacks details on scope, safety, or potential side effects beyond the sync operation.

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, front-loads the main purpose, then gives usage context. No wasted words.

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 tool with no parameters and no output schema, the description captures purpose and usage adequately. Could mention prerequisites or error handling, but not essential.

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?

No parameters exist, so the description cannot add parameter information. Schema coverage is 100% by default, so baseline 4 is appropriate. The description does not need to explain parameters.

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?

Clearly states the tool syncs data from LanceDB vector store into relational tables. Distinguishes from sibling ingest/query tools by specifying 'after ingesting documents to make relational queries up to date'.

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?

Explicitly recommends calling after ingestion and notes idempotency allows anytime use. Does not specify when not to use, but the idempotent nature makes it safe.

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