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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is well covered. The description adds useful behavioral context beyond those annotations: it states what the tool returns ('claimed org/user accounts') and clarifies the app's role (reads/opens PRs) and its distinction from GitHub Copilot MCP. It does not discuss side effects or edge cases, but the annotation coverage lowers the burden.

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 front-loaded with the purpose, then the return value, then identity disambiguation and routing. Every sentence provides useful information, though the Routing block slightly repeats the 'if not connected, call start_github_app_claim' instruction. It is efficient and well-structured overall.

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 simple, read-only, one-parameter tool with no output schema, the description covers the purpose, return content, usage timing, and routing to the correct fallback tool. It explicitly names the alternative tools and conditions. Nothing essential is missing for an agent to call it correctly.

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 companyId parameter already has a clear description including the membership requirement. The main description reinforces that the check is 'for this company' but does not add new details about the parameter's format, source, or usage beyond what the schema provides. Baseline 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?

The description clearly states a specific verb and resource: 'See whether GetFreedomOS (the FreedomOS GitHub App) is connected for this company' and specifies the output ('Returns claimed org/user accounts'). It also differentiates the tool from GitHub Copilot MCP and start_github_app_claim, so an agent can identify it among siblings without opening the schema.

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?

Usage guidance is explicit: 'If not connected, call start_github_app_claim. Use before starting a new connect flow.' The Routing block further encodes a decision tree: connected → this tool, not connected → start_github_app_claim, and Copilot MCP → list_integrations. This is an exemplary when-to-use vs alternatives explanation.

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