get_sync_context

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

With no annotations, the description must carry behavioral disclosure. It reveals the offline-first behavior and optional remote pull. However, it does not state whether the tool modifies local state, what happens on error (beyond returning local data), or any permission or side effects.

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 sentences with no filler. The first sentence states the primary action, and the second adds a critical qualifier. Every word is meaningful and front-loaded.

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 (which presumably documents return values), the description covers the essential behavior and key constraints. It is sufficient for an agent to understand the tool's role, though terms like 'local session state' and 'compiled truth' could be clarified further.

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 the description should compensate. It only hints at the 'refresh_remote' parameter ('Optionally pull remote truth first'), but provides no context for 'agent_name' or 'project_name'. Only one of three parameters receives any semantic value.

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 tool loads local session state and compiled truth, with optional remote pull. The verb 'load' and resources 'session state' and 'compiled truth' are specific, and the offline-first behavior distinguishes it from related tools like pull_truth.

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 use for offline-first scenarios ('always returns local data') but does not explicitly state when to use this tool versus siblings like pull_truth or sync_offline_facts. No guidance on when not to use or prerequisites.

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