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

Beyond the annotations' write/open-world/destructive hints, the description discloses the actual multi-step flow: the tool returns an install_url, the operator must complete the browser-side org/repo selection, and Pulse later finishes the bind. It also clarifies that GitHub-side installation is not performed by this tool, describes repeat behavior when already connected, and explains approval-persistence semantics.

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 information-dense and well ordered: purpose first, then the browser flow, then routing, then approvals. It contains no filler or tautology, and every sentence contributes actionable context for an agent.

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?

For a one-parameter tool with no output schema, the description covers the key return value (install_url), the status-plus-URL behavior when already connected, the human-in-the-loop requirement, and approval semantics. Nothing essential for correctly invoking and completing the flow is missing.

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 single parameter companyId is already fully documented in the input schema with 100% coverage, so the description is not required to repeat parameter details. It adds no parameter-specific semantics beyond the schema, which fits the baseline-3 case.

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 action ('Start connecting GetFreedomOS... for this company') and a concrete deliverable (returns an install_url that the operator opens in a browser). It also explicitly distinguishes itself from request_connector GitHub and GitHub Copilot MCP, so an agent can differentiate it from siblings.

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?

It gives an explicit 'Use when' condition for binding GetFreedomOS onto a GitHub org/repo, plus a routing rule ending with 'Not request_connector GitHub.' It also provides operational guidance about when to call it in the approval flow ('Call it on the first clear ask; the card is the yes — do not re-ask in chat').

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