connect_stripe

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

No annotations provided, so description must fully disclose behavior. It states the return value and a requirement, but omits side effects (e.g., does it create database records, trigger emails?), permissions needed, and what happens if onboarding is already in progress. For a mutation tool, this is insufficient.

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?

Single sentence with no redundant information. The essential information (action, resource, return, requirement) is front-loaded and efficiently conveyed.

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?

For a simple tool with 2 parameters and no output schema, the description covers the basic purpose and a requirement. However, it lacks details on error handling, idempotency, prerequisites beyond tier, and what happens after the redirect. Adequate but could be improved with a couple more sentences.

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?

Schema coverage is 50% (return_url described, project_id not). The main description does not add any parameter details beyond what the schema provides. It mentions 'for a project' but does not explain project_id or how return_url is used, leaving half the parameters underdocumented.

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?

Clearly states the verb 'Start' and resource 'Stripe Connect onboarding', and specifies it returns an onboarding URL. Distinguishes from sibling tools like disconnect_stripe and get_stripe_status by focusing on the onboarding initiation.

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?

Mentions a prerequisite (Starter+ tier), which helps the agent know if the tool is applicable. However, it lacks explicit guidance on when not to use (e.g., if already onboarded) or alternatives. Still provides useful context for selection.

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