madeonsol_copytrade_update

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

Annotations provide basic info (non-read-only, non-destructive, non-idempotent), but the description adds little beyond stating it updates fields. No disclosure of side effects, permission requirements, or whether updates are partial or full replacements.

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?

A single concise sentence that conveys the core purpose without fluff. Could be slightly more structured, but effective for its brevity.

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?

Given the tool's complexity (10 parameters, 3 enums, no output schema), the description lacks completeness. It does not explain update behavior (e.g., partial updates, validation rules, response format), which is critical for correct invocation.

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 has 10 parameters with only 10% description coverage (only 'id' described). The description mentions 'fields... including is_active toggle' but fails to explain the meaning or constraints of the other 9 parameters, leaving the agent with minimal guidance.

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 verb 'Update' and the resource 'copy-trade rule', and it distinguishes from sibling tools like create, delete, get, list by focusing on modification. The mention of 'including is_active toggle' adds specificity.

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 use this tool versus alternatives (e.g., create or delete). No prerequisites, exclusions, or context about when to update vs recreate a rule.

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