set_org_payout_wallet

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

No annotations provided, description fully discloses mutation (PATCH), authorization requirements, preconditions (wallet must be linked to org), and response fields (recovery.status, active_wallet_count, next_actions).

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 tightly written paragraph with no unnecessary words. Front-loaded with purpose and key constraints.

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 two-parameter mutation tool with no output schema, the description covers purpose, parameters, behavior, and response fields comprehensively.

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 100%, so baseline is 3. Description adds some context (wallet must be active, null to clear) but does not provide significant new semantics beyond schema descriptions.

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 action: set or clear an organization's default payout wallet for tenant priced routes, with HTTP method and path. Distinguishes from siblings by specifying the specific resource and operation.

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?

Specifies admin/owner-only and step-up gating, along with conditions for wallet_address (must be active wallet or null). Provides clear context but does not explicitly compare with alternative tools.

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