convert_to_assets

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

With no annotations, the description must disclose behavioral traits. It only says 'Convert,' implying a mutation but without stating side effects (e.g., whether shares are destroyed, fees, reversibility). This is insufficient for a mutation tool.

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?

The description is very concise (6 words) and front-loaded. Every word contributes, but it may be too brief, lacking important context. Still, it avoids fluff and is efficient.

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 simplicity (1 param, no output schema, no annotations), the description is incomplete. It does not explain conversion rate, return format, or side effects. For a mutation tool, more detail is needed to ensure 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 one parameter 'shares' with no description coverage. The description adds meaning by indicating the shares are wSTASIS and the output is STASIS value. However, it does not specify units, range, or conversion implications, so it adds minimal additional value.

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 (convert) and the resource (wSTASIS shares to STASIS value). It distinguishes this tool from siblings like get_my_shares or stake/unstake operations, though the exact nature of conversion (e.g., exchange rate) is not clarified.

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. No prerequisites or conditions are mentioned, leaving the agent uncertain about context (e.g., whether shares must be owned, if conversion is always available).

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