Lulo Get Best Rates

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

Annotations (readOnlyHint, idempotentHint, no destructive) already indicate safe, read-only, idempotent operation. Description adds no contradiction but also no extra behavioral details beyond basic purpose. Adequate given annotation coverage.

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?

First sentence is concise and front-loaded. Second sentence about SAP MCP context is tangential and adds length, reducing conciseness. Overall acceptable but not optimal.

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?

Tool has output schema and annotated behavior. Description does not clarify behavior when optional mint parameter is omitted (e.g., returns rates for all tokens?). Missing detail on caching or update frequency. Adequate but could be more complete.

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% with one parameter 'mint' well-described. Description adds no additional meaning beyond what schema provides. Baseline 3 applies.

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?

Description clearly states the verb 'get', resource 'best lending/yield rates', and scope 'across all protocols via Lulo'. Distinct from sibling lulo tools which involve depositing, withdrawing, or getting positions.

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?

Description includes SAP context instructions but does not specify when to use this tool vs alternatives (e.g., other lulo tools or rate tools like jupiter_getQuote). No when-to-use or when-not-to-use guidance.

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