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

Annotations declare openWorldHint and non-destructive, but the description adds the key behavioral trait: it opens the person's browser and requires their session and consent. The two-call pattern is disclosed, including that a later call reports the connected account. This meaningfully enriches the annotations without contradicting them.

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?

Two concise sentences with no wasted words: the first states the purpose and the second explains the interactive flow. Everything present earns its place.

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?

The output schema exists, the parameter is fully documented, and annotations cover the safety profile. The description covers the critical flow: browser interaction, user consent, and repeated invocation, so an agent knows exactly what to expect.

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 schema fully covers the single `platform` parameter with a clear description and enum, so baseline 3 applies. The description adds no extra parameter details beyond what the schema already provides.

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 action ('Connect a social account') and elaborates on the browser-based linking flow. It implicitly distinguishes itself from accounts_list and accounts_performance by describing the connect interaction rather than listing or analytics.

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 provides clear operational guidance: invoke the tool, let the user sign in externally, then invoke again afterward to get the result. It explicitly notes that the sign-in part 'cannot happen here,' setting correct expectations. It does not name explicit alternative tools or exclusions, but the context is sufficient.

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