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

With no annotations supplied, the description carries the behavioral burden. It clearly indicates a read-oriented status check using 'See whether' and 'Returns', and adds helpful behavioral context about what the app does (read/open PRs) and what the tool returns (claimed org/user accounts). It doesn't explicitly state that the call has no side effects or describe error conditions, but the read-only intent is strongly conveyed.

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 front-loads the core purpose and return value, then gives a routing paragraph. It is clear and focused, though there is some duplication: 'If not connected, call start_github_app_claim' appears twice. Still, the prose is dense enough to earn its place by disambiguating similar tools.

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 single-parameter status tool with no output schema, the description gives the essential complete picture: what the tool checks, what it returns, which app it refers to, when to use it, and which sibling to fall back to. The context needed to invoke it correctly is largely present.

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 input schema already fully documents companyId with 'FreedomOS company id, required, membership requirement, and company-scoped tools context', so schema coverage is 100%. The description only adds 'for this company', which doesn't add meaningful parameter semantics. This meets the baseline but adds no real extra value to the parameter meaning.

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 names a specific action and resource: checking whether the FreedomOS GitHub App is connected for a company, and states it returns claimed org/user accounts. It clearly distinguishes itself from GitHub Copilot MCP and from start_github_app_claim, so an agent can select it 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?

The description explicitly says when to use this tool: before starting a new connect flow, and as the routing decision point for whether the app is connected. It also names the exact alternatives and conditions: call start_github_app_claim if not connected, and list_integrations for GitHub Copilot MCP. This leaves no ambiguity.

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