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

Annotations declare readOnlyHint=false and destructiveHint=false, so the mutation/non-destructive profile is already covered. The description adds meaningful domain behavior—this is a funding vehicle where stakers accrue future protocol fees—but says nothing about permissions, whether the pool is mutable afterward, or what happens when a pool is created twice for the same capability.

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 short sentences, action first, purpose second. No filler, no redundancy, and the key noun phrase is front-loaded.

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 4-param mutation with no output schema and only partial behavioral annotation coverage, the description is adequate but thin. It omits prerequisites, duplicate-pool handling, and what a successful call yields; the schema covers parameters at 100% but does not compensate for behavioral gaps.

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 all four parameters (currency, description, targetAmount, capabilityType) are already documented in the schema. The description adds no syntax, default, or format detail beyond it, which is the expected baseline when the schema does the heavy lifting.

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 investment pool') plus the domain intent (funding a capability bounty, stakers earn future protocol fees). It is more than a restatement of the name. However, it does not distinguish itself from close cousins like convert_bounty_to_pool, stake_in_pool, or create_capability, so sibling differentiation is missing.

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 converting an existing bounty to a pool or staking into one, and no prerequisites (e.g., whether the capability must exist first). The agent gets domain context but no routing logic.

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