delimit_tracker_sync

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

Description clearly discloses read-only behavior and that it enriches the ledger. No annotations are provided, so the description carries the full burden. It could mention potential side effects on the ledger, but overall it's transparent.

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?

Three concise sentences with no wasted words. First sentence states action, second clarifies read-only, third emphasizes no write-back. Well-structured and front-loaded.

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 that an output schema exists, the description adequately covers input and behavior. It could mention auto-detection of repo when empty, but that is already in the schema. Generally complete for a simple sync 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 coverage is 100% with good parameter descriptions. The tool description does not add additional parameter-level details beyond what the schema already provides. Baseline score of 3 is appropriate.

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?

Clearly states it pulls open issues from GitHub into the Delimit ledger. Uses specific verb 'pull' and resource 'open issues'. Explicitly notes read-only nature, distinguishing from sibling tools that might write back.

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 states 'Read-only sync' and 'Does NOT write back to GitHub', providing clear context for when to use. However, does not specify alternatives or when not to use, though the contrast is evident.

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