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

While annotations confirm it is read-only, the description adds crucial behavioral context like 'Early access', the specific credential requirement ('Last Price credential with billing read scope'), and the failure state regarding sandbox keys, which are behaviors not captured by simple hints.

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 definition is densely packed with highly specific information regarding prerequisites and behaviors. While it could benefit from bullet points for maximum readability, every sentence provides essential, non-redundant value.

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 the high complexity (requiring specific credentials, workspace claims, and being in an early access phase), the description is highly complete. It provides all the necessary environmental and functional context for an agent to invoke the tool safely.

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?

Since the tool has 0 parameters and 100% schema coverage, the description must carry all semantic weight. It successfully explains the scope of the read operation and the operational context surrounding the connection, providing significant informational value despite the lack of structured parameters.

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 defines the resource and the action: it reads the current Stripe connection status, account ID, and mode. It is distinct from other payment or billing tools in the sibling list by its explicit focus on Stripe.

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 definition includes critical usage context, such as the requirement for 'a person in a browser' for connection, and explains the operational state necessary for the tool to work (e.g., workspace must be claimed, or a 403 error is expected).

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