sync_to_sql

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

Annotations already declare readOnlyHint=true, but the description adds substantial behavioral context: the cache is in-memory and session-scoped ('gone when this session ends'), it auto-clears when the open company changes (regardless of how), and the return message discloses when that happens. It also explicitly excludes vouchers. These are critical runtime behaviors not captured in structured metadata.

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 multi-sentence but every clause earns its place: purpose, cache lifecycle, company-change safety, and exclusion of vouchers. The most important purpose is front-loaded, and the exclusion is at the end where it serves as a natural pointer. No redundant filler.

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 no-parameter, no-output-schema tool, the description is fully complete. It covers what data is synced, why it exists (fast queries), how long it persists, how staleness is prevented, what it doesn't cover, and which sibling to use instead. An agent has everything needed to invoke it correctly and understand side effects.

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 an empty schema, so there is nothing to document. The baseline for 0 params is 4; the description correctly does not invent parameters and instead explains the tool's operation. It adds no parameter-specific semantics because none exist, which 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?

The description opens with a clear verb-resource pair ('Pull ledgers, groups, and stock items from TallyPrime into this session's SQL cache') and immediately differentiates from siblings by explicitly stating what it does NOT do ('Does NOT sync vouchers – use sync_vouchers_to_sql'). This gives an agent an unambiguous mental model of the tool's scope.

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 states when to use the tool: to enable fast arbitrary queries via query_sql without repeatedly hitting Tally. It also names the alternative for vouchers (sync_vouchers_to_sql) and even clarifies the one-date-range-at-a-time behavior of that alternative. The conditions for using this tool vs alternatives are explicit and actionable.

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