Jito Get Tip Estimate

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint false, so the description adds no significant behavioral details beyond restating the tool's read-only nature. No contradictions are present.

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 first sentence is concise and front-loaded, but the second sentence about SAP context is irrelevant and verbose, reducing overall conciseness. The description could be trimmed to only the essential first sentence.

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?

The core functionality is covered, but the inclusion of extraneous SAP context about registering agents and publishing tools makes the description less focused. With an output schema present, return values need not be explained, but the description still introduces unnecessary noise.

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 no parameters, so the description does not need to add parameter meaning. Baseline is 4, and the description appropriately omits param information.

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 starts with a specific verb 'Get' and clearly identifies the resource as 'current Jito tip percentile estimates for bundle inclusion priority'. This distinguishes it from sibling tools like jito_getBundleStatus and jito_sendBundle, which serve different purposes.

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 implies the tool should be used when needing Jito tip estimates for bundle priority, but provides no explicit guidance on when not to use it or alternatives. The SAP context paragraph discusses unrelated tool registration and detracts from usage clarity.

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