survey

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

With no annotations, the description discloses the stale flag semantics, age_hours, and the AGENTSYNC_STALE_HOURS default, and clarifies it reports on *other* agents only. It does not explicitly state read-only behavior, but 'Pull' implies non-mutating.

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 paragraphs, every sentence adds value; front-loaded with the core function, then flags and usage.

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-input read tool with an output schema, the description covers the important output semantics (stale flag, default threshold, scope) and provides usage guidance; nothing obvious missing.

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 input schema has zero parameters, so the description needn't explain any. Baseline 4 applies since there's nothing to document.

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 'Pull[s] the latest coordination state' and enumerates the specific fields reported (task, files touched, dependencies, branch, status, timestamp), distinguishing it from sibling tools like claim, release, or check_conflicts.

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 says 'Call this before planning and again after finishing work,' giving clear timing. It also notes it works for any number of collaborators, but does not explicitly name alternatives or when-not to use.

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