deposit_jst_for_votes

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

Disclosures match annotations (destructiveHint=true) and add value by stating that deposited JST can be withdrawn after voting. No contradiction.

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 concise sentences covering action, prerequisite, conversion, and reversibility. No fluff.

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?

Complete for its complexity: explains workflow, prerequisites, conversion, and withdrawal. Aligns well with sibling tools.

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 100% coverage for parameters. Description adds meaning with '1 JST = 1 Vote', clarifying the impact of the 'amount' parameter beyond schema description.

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 action (deposit), resource (JST into WJST contract), and purpose (get voting power). It distinguishes from sibling tools like 'approve_jst_for_voting' and 'withdraw_votes_to_jst'.

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?

Explicitly states prerequisite (use approve_jst_for_voting first), guiding the agent on the correct sequence. Lacks explicit 'when not to use' but provides clear context.

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