lst_to_near_rate

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

No annotations are provided, so the description must carry the behavioral disclosure burden. The verb 'Get' strongly implies a read-only operation, and the description clarifies the rate semantics and the optional amount behavior. However, it does not disclose data sources, freshness, failure modes, or any operational constraints, leaving some behavioral uncertainty for a tool with zero annotation support.

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 a single focused sentence that front-loads the core action and result. The parenthetical clarification ('how much NEAR your stNEAR/LiNEAR is worth') earns its place by making the tool's value concrete. There is no redundant text, and it is highly scannable.

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 simple rate-query tool with three optional parameters and full schema coverage, the description is nearly complete. It explains the core return concept and the optional-amount behavior. The lack of an output schema and any mention of return format is a minor gap, but the tool's purpose is straightforward enough that an agent can invoke it confidently.

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 description coverage is 100%, so the baseline is 3 even without additional parameter explanation in the description. The description adds minor value by naming stNEAR/LiNEAR as concrete LST examples, but the amount, network, and protocol semantics are already fully documented in the input schema. No parameter meaning is missing or obscured.

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 uses a specific verb and resource: 'Get current exchange rate between LST tokens and NEAR.' It also grounds the abstraction with concrete examples ('stNEAR/LiNEAR'), making it clear this is a rate-conversion tool rather than a balance, staking, or APY tool. This distinguishes it from the related sibling tools without requiring the agent to open any schemas.

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?

The description explains what the tool does but provides no guidance on when to choose it over siblings such as compare_lst_providers or get_staking_apy. There is no mention of when this tool is appropriate versus when another tool would be better, and no exclusions or alternative routing. Usage must be inferred entirely from the tool name and the sibling list.

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