get_best_restaking

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

Describes scoring dimensions (TVL, audits, age) and coverage, but could elaborate on what 'best' means or if it's read-only. No annotations to verify idempotency.

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?

Two clear paragraphs: first states purpose and scope, second provides usage guidelines. No superfluous content.

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?

Covers purpose, scope, criteria, and usage boundaries. Output schema likely details return format, so no additional info needed.

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 covers 100% of parameters; description adds threshold values for risk_profile and enum details for restaking_type, enhancing schema descriptions.

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?

States specific verb 'Select' and resource 'best restaking protocol', lists covered protocols (EigenLayer, Symbiotic, etc.), and explicitly distinguishes from sibling 'get_best_liquid_staking'.

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?

Provides explicit when to use ('agent wants to restake ETH or LSTs') and when not to use ('simple staking' with alternative tool named). Also outlines scoring criteria (TVL, audits, age).

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