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

Annotations provide no positive hints (all false), so the description carries the burden of behavioral disclosure. It covers the return value, browser-based approval flow, polling requirement, and the 10-minute link expiration. It could explicitly mention whether calling repeatedly invalidates previous links or whether there are side effects beyond issuing a link, but the provided details are useful.

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. The first sentence states the purpose, the second explains the return value and user flow, and the third covers expiration and re-invocation. Every sentence earns its place with no redundancy.

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 zero-parameter tool with an output schema, the description is complete. It explains the returned install_url, the browser flow, how to detect successful connection via get_onboarding_status, and the expiration behavior. Nothing essential is missing for an agent to invoke and handle the result 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?

The tool has zero parameters, so the description does not need to explain parameter meaning. The description still adds value by clarifying what the return value represents and the external action it triggers, which is more than necessary for a parameterless tool.

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 verb and resource: getting a link that connects a GitHub account so work can reach real repos. It clearly differentiates from siblings like list_github_repos and get_onboarding_status by focusing on initiation of GitHub connection.

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 explains when and how to use the tool: send the returned install_url to the user, wait for them to approve in the browser, then poll get_onboarding_status until github_connected is true. It also covers link expiration and the need to call connect_github() again, which is clear operational guidance.

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