sync_offline_facts

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

With no annotations, the description must disclose behavioral traits. It indicates flushing (likely destructive to the queue) and optional consolidation, but does not explain side effects (e.g., deletion of local queue, network requirements, error handling).

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 single-sentence and concise, but it sacrifices completeness. It could be expanded without losing conciseness.

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 presence of an output schema (not shown) and 2 parameters with 0% schema coverage, the description is far from complete. It fails to explain agent_name, consolidation details, or behavioral implications, leaving significant 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 description coverage is 0%. The description only hints at the 'consolidate' parameter ('optionally consolidate'), but does not mention the required 'agent_name' parameter or explain its purpose. This is inadequate for tool usability.

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 it flushes the offline queue to remote, with optional consolidation and pulling truth. It distinguishes from siblings like pull_truth (which likely pulls without flushing) and queue_durable_fact (which enqueues). However, the phrase 'consolidate + pull compiled truth' is somewhat vague.

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?

No explicit guidance on when to use this tool versus alternatives like pull_truth or queue_durable_fact. No prerequisites or exclusions mentioned.

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