get_sync_context

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

With no annotations, the description carries full transparency burden. It discloses the offline-first guarantee and optional remote pull, but omits details about side effects, error handling, or what 'compiled truth' means.

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 very concise (two sentences) and front-loaded with the primary action. No redundant or verbose text.

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?

Despite having 3 parameters and an output schema, the description leaves out parameter details and fails to clarify what 'compiled truth' or 'session state' means. It is not fully complete given the tool's complexity and sibling context.

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 explain parameters. It only hints at the 'refresh_remote' parameter via 'optionally pull remote truth first', ignoring 'agent_name' and 'project_name'. Meaningful mapping is missing.

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 an option to pull remote truth first. It is a specific verb+resource, but does not explicitly differentiate from sibling 'pull_truth' beyond the offline-first hint.

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 mentions offline-first behavior and that local data is always returned, but does not provide explicit guidance on when to use this tool versus alternatives like 'pull_truth' or 'sync_offline_facts'.

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