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

Annotations already flag destructiveHint=true and openWorldHint=true, but the description adds needed behavioral context: the signing scheme (X-Agent-Id/X-Signature/X-Timestamp), that the owner session token also authorizes, that signing works on both transports, and that signatures are single-use on the SSE channel. It does not explain what a disconnect destroys, which would be the main remaining gap.

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?

Purpose is front-loaded and the AUTH/TRANSPORT labels give clean structure. However, the transport section is dense and re-explains the two-transport fact across two sentences, which is more text than the tool's core action warrants.

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?

No output schema exists, yet the description never explains what the 'status' mode returns or what a 'disconnect' removes, both of which an agent needs for a destructive, tri-modal tool. Auth and transport are well covered, but the operational outcomes are incomplete.

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 repo/owner/token/action/agent_id/project_id are already documented in the schema. The description adds essentially no parameter-level detail beyond what the schema provides, so the baseline of 3 applies.

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?

States a specific verb and resource ('connect/check/disconnect a GitHub repo from a handoff project') and explains the downstream effect (goals become branches, tasks become commits/PRs, wall posts become issues). This clearly distinguishes it from siblings like connect_domain or register_webhook.

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 three modes (connect/check/disconnect) are only implied by the parenthetical and the schema enum; the description never states when to pick status over disconnect or what preconditions select each. No alternatives or exclusions are named.

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