connect_status

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

Annotations already note idempotent and non-destructive. The description adds that on success the account token is stored locally (never shown in chat) and seller tools start working, which provides behavioral context beyond annotations. No contradiction.

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 sentences, no wasted words. Front-loaded with purpose, every sentence contributes value. Extremely concise.

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?

Given no parameters and no output schema, the description adequately covers the pairing flow, success behavior, and activation of seller tools. However, it could mention failure cases or what happens if the approval hasn't occurred.

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 has 0 parameters (100% coverage), so the description need not add parameter details. It uses no-parameter design effectively, and the description explains the tool's purpose without needing param info.

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 that the tool finishes or checks account pairing started by connect_account, and distinguishes it from its sibling tool connect_account. The verb 'check' or 'finish' is specific to this resource.

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 to call it after the user approves in the browser, providing a clear when-to-use. It also implies that it should be used after connect_account. However, it does not explicitly mention when not to use or alternatives.

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