jito_getTipEstimate

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

Since no annotations are present, the description must convey behavioral traits. It indicates a read operation ('Get') and specifies the output ('percentile estimates'). However, it does not disclose authentication needs, rate limits, or any potential side effects. The description adds basic context but lacks depth for a no-annotation 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 a single sentence of 12 words, conveying the essential purpose without any extraneous information. It is perfectly concise and front-loaded.

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 has no parameters, no output schema, and is a simple read operation, the description provides sufficient context for an agent to understand its function. It could optionally describe the output format (e.g., values or percentiles), but the current description is mostly adequate.

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?

The input schema has zero parameters, with 100% schema description coverage. With no parameters, the description doesn't need to add parameter meaning. For a no-parameter tool, a baseline score of 4 is appropriate.

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 tool retrieves current Jito tip percentile estimates for bundle inclusion priority. It uses a specific verb ('Get') and resource ('Jito tip percentile estimates'), distinguishing it from sibling Jito tools like jito_getBundleStatus and jito_sendBundle.

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 is provided on when to use this tool compared to alternatives. There is no mention of prerequisites, when not to use it, or scenarios where another tool might be more appropriate.

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