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

Despite having no output schema, the description discloses the return payload (store URL, private dashboard link, agent_key) and its downstream use. It also adds security-critical context not in the annotations: the wallet must be a public address, never a secret key, and test mode substitutes a demo address when omitted.

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?

Three sentences, each doing distinct work: purpose, prerequisites, and parameters plus returns. The purpose is front-loaded and nothing is repeated from the name or title.

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 non-idempotent, open-world creation tool with no output schema, the description covers purpose, prerequisites, return values and the credential hand-off. It omits what happens on failure or on repeated invocation (the annotation flags idempotentHint=false but the description never warns that re-calling creates another store).

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 the baseline is 3, but the description genuinely adds meaning: it clarifies that wallet is optional, constrains it to a public address with an explicit prohibition on secret keys, and explains the test-mode fallback. It does not add format/syntax hints beyond the schema's example.

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?

The opening sentence states a specific verb and resource ('Open a new Ripey store') and the closing sentence establishes its role as the onboarding/credential-minting step for the other Ripey tools. That makes it trivially distinguishable from siblings like create_product or sales_summary, which operate inside an existing store.

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?

'Ask for the store name and the user's email first' and 'pass it to the other Ripey tools on this same connection' give explicit preconditions and a clear hand-off to the siblings. It stops short of stating when NOT to call it (e.g. what to do if the user already has a store), so it is not a full 5.

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