bb_sync_status

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

No annotations are provided, so the description carries the full burden. It usefully discloses the two behavioral states (in-progress progress vs. terminal result), which is real signal. It omits other relevant behavior: whether the call blocks, whether it errors if no sync has ever run, and whether the result persists across sessions.

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?

A single compact sentence with the two modes stated up front and no filler. The parenthetical is slightly awkward but costs the reader almost nothing.

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?

With no annotations and no output schema, the description is the only source of information about the return value, yet it only gestures at 'progress' or 'the result' without characterizing either shape or the fields an agent should expect. For a status-polling tool this is adequate but leaves a meaningful gap.

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 takes zero parameters, so the baseline is 4. Nothing in the description distorts or contradicts the empty schema.

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 states a specific resource (bb_sync) and what the tool returns: progress while a sync runs, or the result of the last sync. That is clear enough for an agent to know this is a status/result reader. It does not, however, differentiate itself from the sibling bb_status, which could plausibly also be read as a status tool.

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?

There is no explicit when-to-use guidance, no prerequisite stating a sync must first be started with bb_sync, and no mention of the alternative (bb_status) or when to prefer it. The temporal framing ('while running' / 'most recent') implies usage but leaves the agent to infer the trigger conditions.

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