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

Annotations already declare the safe read-only, closed-world profile, and the description goes beyond them by disclosing the payload shape ({ connectUrl, items: [...] }) and the ready/status semantics, plus the actionable recovery step when a connection is missing. That is real behavioral context an agent cannot derive from the annotations.

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?

Four short sentences, front-loaded with purpose, then the routing rule, then the return shape, then the edge-case remedy. Nothing is padding; the payload sentence is earned because there is no output schema.

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?

With no output schema, the description takes on return-value disclosure and does it, including the connectUrl field and item fields. Combined with the usage trigger and failure handling, an agent has everything needed to call and act on this tool.

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 a single parameter and 100% schema description coverage ('From workspace_list.'), the schema already carries the meaning. The description adds no workspaceId syntax or constraints, so the baseline 3 applies.

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 ('List the Stripe and Cal.com accounts the workspace has connected'), narrowing scope to payment/booking providers, which cleanly separates it from the many form/editor/request siblings. An agent knows exactly what this returns without opening the schema.

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?

Gives an explicit trigger ('Read before request_create with a payment or booking block'), which is a concrete when-to-use rule tied to a named sibling. It also handles the negative case ('Missing or not ready: tell your user to open connectUrl once'), so both the call condition and the failure path are specified.

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