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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds real context beyond that: it reveals the tool operates on the "connected key" (implying prior integration setup) and that the response includes live/test mode, which matters for interpreting downstream results.

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 short sentences, zero waste. The output content is stated first and the sequencing instruction follows, so the function is front-loaded.

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?

No output schema exists, yet the description enumerates the key return values (name, id, mode) and the operational precondition. For a zero-parameter connectivity check, nothing an agent needs is missing.

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?

With zero parameters, the baseline of 4 applies. The description correctly implies a no-argument call and adds no misleading parameter expectations.

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?

Names a specific verb (check) and resource (which Stripe account the connected key belongs to), and enumerates the returned fields (name, id, live or test mode). That scope cleanly separates it from siblings like stripe_api_details, stripe_api_read, or the summary tools, which operate on payment data rather than connection identity.

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?

"Run this first to confirm the connection" gives explicit ordering guidance and a clear trigger condition. There are no stated exclusions or named alternatives, but the "first" framing makes the usage context unambiguous for a setup/verification step.

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