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

Annotations indicate write operation (readOnlyHint false) and non-destructive (destructiveHint false). Description adds important behavioral context: permission checking, free business restriction, and warning steps. Does not detail side effects like immediate effect or configuration loss, but sufficient for a configuration update.

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?

Five sentences with front-loaded purpose. Each sentence adds value, but the clarification 'Business and community refer to the same thing' could be more precise. Still efficient and clear.

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?

Complex tool with 3 parameters, nested objects, no output schema. Description covers preconditions and access rules well but omits parameter explanations and expected return value. Agent would lack critical info to invoke correctly.

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 description coverage is 0%, and description provides no information about the three parameters (metadata object, communityId, payoutAccountType). No valid values or formats explained. The description fails entirely to add meaning beyond the raw schema.

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 tool updates Stripe Connect payout account configuration. Distinguishes from siblings like create_community_payout_account (create vs update) and update_business_stripe_connect_account. Clarifies that 'business' and 'community' are interchangeable, though slightly confusing.

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?

Provides explicit before-use instructions: check business permissions, free businesses cannot use, call check_business_tool_access, show grace-period warning and resubscribe link, and never proceed when access is blocked. Clearly communicates when NOT to use the tool.

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