delimit_tracker_sync

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

Since no annotations exist, the description carries the full burden. It discloses side effects: read-only on GitHub (network calls via gh CLI) and writes context entries into the ledger without pushing back. This covers key behaviors. A minor gap is lack of detail on failure modes or response format, but output schema handles return values.

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 highly structured with clear sections: main purpose, when to use, when not to use, sibling contrast, side effects. Every sentence adds value, no fluff. It is concise yet comprehensive.

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 tool has 3 parameters (none required), no annotations, but an output schema, the description fully covers purpose, usage guidelines, behavioral side effects, and sibling differentiation. No additional information seems necessary for an agent to correctly select and invoke this tool.

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 100%, so all three parameters have descriptions in the schema. The tool description does not add extra meaning beyond the schema, consistent with the baseline of 3 for high coverage. No additional context is needed.

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 pulls open GitHub issues into the Delimit ledger as context. It uses a specific verb ('Pull'), resource ('open GitHub issues'), and outcome ('into the Delimit ledger as context'). The sibling contrast with delimit_sensor_github_issue further clarifies the scope.

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?

Explicit 'When to use' and 'When NOT to use' sections are provided, with clear guidance: use to enrich ledger with external issue context, avoid for write-back to GitHub or monitoring a single issue (use sibling instead). This directly addresses selection among siblings.

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