Delimit Tracker Sync

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

The annotations only say readOnlyHint=false and destructiveHint=false, but the description adds important nuance: it is read-only on GitHub, makes network calls via gh CLI, writes context entries into the ledger, and does not push back. This precisely clarifies the mixed read/write behavior beyond what annotations convey.

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 organized into clear labeled sections: purpose, when to use, when not to use, sibling contrast, and side effects. Every sentence adds useful information, and the structure makes it easy for an agent to scan.

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 100% schema coverage, an output schema, and clear annotations, the description fully covers the behavioral and selection context. It explains side effects, sibling differentiation, and usage boundaries, leaving no critical gap for an agent to infer.

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%, and the schema already documents repo, limit, and labels with defaults and examples. The description does not add parameter-level detail, but it does not need to because the schema carries the burden effectively.

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 verb and resource: 'Pull open GitHub issues into the Delimit ledger as context.' It clearly identifies what the tool does and distinguishes it from the sibling delimit_sensor_github_issue, which watches a single issue rather than syncing many.

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 explicitly says when to use it ('to enrich the ledger with external issue context'), when NOT to use it ('to write back to GitHub' or 'to monitor a single issue'), and names the alternative tool. This gives an agent unambiguous routing logic.

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