paybot_pool_create

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

With no annotations, the description carries full burden and does disclose meaningful traits: the pool is in-process and session-scoped, treasury accounting is in-memory, and the facilitator stays authoritative. It does not say what happens on a duplicate poolId, whether creation is idempotent, or what auth is required for a mutating call.

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?

Two sentences, no filler, and the primary action is front-loaded before the lifecycle caveats. Every clause carries information.

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-param mutating tool with no annotations and no output schema, the description covers lifecycle and authority adequately, but omits duplicate-id behavior, error modes, and interaction with paybot_pool_allocate/revoke that an agent would need to use it 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 100%, so both parameters are already documented, including that poolId is reused by allocate/revoke/status. The phrase 'optional shared daily treasury' loosely maps to sharedDailyLimitUsd but adds no syntax or enforcement detail beyond the 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?

States a specific verb and resource ('Create an in-process bot pool'), plus an optional capability (shared daily treasury). The 'pool' resource clearly separates it from sibling families like paybot_pay or paybot_balance, though no sibling is named explicitly.

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?

No guidance on when to create a pool versus using individual bot spending limits (paybot_set_spending_limit), nor prerequisites such as registration first. The session-lifetime note is context, not usage routing.

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