jito_getBundleStatus

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

No annotations are provided, so the description must disclose behavioral traits. It only states it checks status, which implies a read-only operation, but fails to mention permissions, side effects, or response structure. For a simple check, this is minimal.

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 extremely concise (6 words, one sentence), front-loading the core action. While efficient, it could include a brief detail about the return value without being verbose.

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?

For a simple status check with one parameter and no output schema, the description is nearly sufficient. However, it lacks information about the response (e.g., possible statuses, error cases) which would help an agent interpret the result.

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 description does not add any meaning to the sole parameter 'bundleId' beyond the schema's name and type. With 0% schema description coverage, the description should at least indicate what a bundle ID is or where to obtain it, which is missing.

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 uses a specific verb 'Check' and resource 'bundle status', clearly distinguishing it from siblings like jito_getTipEstimate (for tip estimation) and jito_sendBundle (for submitting bundles).

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 usage context (after submitting a bundle via jito_sendBundle) but provides no explicit when-to-use or when-not-to-use guidance, nor any comparison to alternatives.

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