github_sync_debate

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

With no annotations present, the description carries the full burden of behavioral disclosure. It explicitly states idempotency ('tracks synced turns to avoid duplicates'), the write behavior ('Posts new turns'), and the two API pathways (GraphQL vs REST). It does not mention authentication or rate limits, but the core behavioral risks are covered well.

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 compact and well-structured: purpose first, then behavior, then args, then an operational note. Every sentence adds value and the Args block is easy to scan. There is no filler or repetition of the tool name.

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?

The description is complete for an agent to invoke the tool correctly: all four parameters are semantically explained, the idempotency behavior is disclosed, and the GitHub target ambiguity (discussion vs issue) is resolved. Since an output schema exists, return-value details are not required here.

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 schema provides no property descriptions (0% coverage), so the description must fully compensate. It does: thread_id is explained as the debate thread to sync, repo is given in owner/repo format, target_id distinguishes GitHub node ID from issue number, and target_type is mapped to 'discussion' (GraphQL) or 'issue' (REST). This is exactly the semantic content an agent needs.

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 first sentence uses a specific verb ('Sync') with a clear resource ('debate turns') and destination ('GitHub Discussion/Issue comments'). The follow-up 'Posts new turns as formatted comments with cognition headers' removes any ambiguity about what the tool actually does. It is clearly distinguished from all sibling tools, which are debate-management operations rather than GitHub synchronization.

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 makes the context of use clear: this is the tool for mirroring debate turns into GitHub discussions or issues. It does not name alternatives, but no sibling tool performs GitHub syncing, so exclusion guidance is not necessary. The note about GITHUB_TOOLS_ENABLED=false adds a useful operational condition.

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