Upgrade Derrick plan

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

Discloses the two-step behavior (plan list retrieval vs. immediate URL), confirms non-destructive nature via annotations, and adds context about invoking based on user input. No contradiction with annotations.

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?

Front-loaded with purpose, followed by structured workflow, triggers, and note on language adaptation. Every sentence is necessary and well-organized.

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?

Covers all aspects of the tool: input variants, output (URL or plan list), and usage rules. No missing information for a tool with one optional parameter and no output schema.

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?

Single parameter 'plan' is fully described in schema and description. The description adds meaningful context: when to include vs. omit to trigger different behaviors (return plan list vs. checkout URL). Schema coverage is 100%.

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 description clearly states the tool starts the upgrade/subscription flow and returns a Stripe Checkout URL. It distinguishes from siblings like derrick_account or derrick_credits by focusing on the upgrade action.

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 workflow: call with plan if user specifies one, otherwise call without plan to get list of plans. States to always use this tool for upgrade requests and not to hand out URLs from memory. Lists multilingual triggers.

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