madeonsol_copytrade_create

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

Discloses that webhook_secret is returned only once, which is critical for HMAC signatures. Annotations already indicate a write operation (readOnlyHint=false), so this adds meaningful context beyond annotations. No contradictions.

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 wasted words. Front-loaded with purpose, followed by essential behavioral note and limits.

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 create operation with 8 parameters and no output schema, the description covers purpose, return value caveat, and constraints. Missing error handling or activation details, but adequate overall.

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. The description adds minimal parameter context beyond schema, mainly the limit on source wallets. Does not explain each parameter's meaning beyond what the schema already provides.

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?

Clear verb and resource ('Create a copy-trade rule'), with specific constraints on webhook secret and limits. Does not explicitly differentiate from sibling copy-trade tools (delete, update, etc.), but the verb is distinct enough.

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?

Implies usage for creating rules, but no explicit guidance on when to use this versus alternatives like update or delete. No 'when not to use' or prerequisites mentioned.

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