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

Adds behavior beyond annotations: the auth code is exchanged server-side, a demo connect link is returned when Google sign-in is disabled, and explicit output-presentation constraints (show only sayToHuman + url, never expose inboxId or raw JSON). Annotations cover the openWorld and non-idempotent nature, so this extra context is valuable and earns a 4.

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?

Three short sentences, front-loaded with the core purpose; the demo-link fallback and disclosure rules each add distinct value. Slightly cluttered by presentation instructions but nothing is wasteful.

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 purpose, fallback behavior, and the shape of the response (sayToHuman + url plus server-side exchange), which is enough to call it correctly. The main gap is the unexplained inboxId semantics.

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?

Single parameter with 0% schema description coverage, and the description only mentions inboxId in the context of hiding it from the human. It never explains that inboxId identifies which inbox to authorize. The description fails to compensate for the schema gap.

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: 'Returns a Google sign-in URL.' An agent can tell it gets an OAuth sign-in link for Google. It does not explicitly distinguish itself from the sibling start_microsoft_oauth, though the Google specificity makes the distinction inferable.

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?

Mentions the fallback condition ('If Google sign-in is not enabled, returns a demo connect link'), which implies usage, but gives no explicit when-to-use guidance or routing versus start_microsoft_oauth / propose_connection. Usage is implied rather than stated.

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