jito_tip_calculator

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

No annotations provided, but description discloses paid nature, x402 authorization requirement, and fallback behavior. Includes input constraints (slot_probability range) and output description.

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?

Concise 5-sentence paragraph. Purpose is front-loaded. Every sentence adds necessary information without redundancy.

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?

No output schema, but description covers return values (tip lamports + EV breakdown), all inputs, and payment mechanism. Sufficient for an agent to use correctly.

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%, so baseline 3. Description adds units (USD, [0..1]) and explains the role of _payment. Also mentions return format, which helps interpret inputs.

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?

Clearly states 'Compute an expected-value-maximizing Jito tip for a Solana arbitrage bundle.' Verb and resource are specific. No sibling tool overlaps with this domain.

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?

Explains when to include the payment parameter and what happens without it. Context is clear, but no explicit when-to-use vs alternatives since siblings are unrelated.

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