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

With no annotations present, the description carries full responsibility for behavioral disclosure. It does not explicitly state that this is a read-only query, how it handles RPC errors, or what the default behavior is regarding the optional URL parameter, aside from the schema's mention of defaults.

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 concise phrase that lists all relevant output fields without any fluff or repetition. It is front-loaded and adequately sized for the tool's simplicity.

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 simple nature of the tool (one optional parameter, no output schema), the description provides a clear list of returned values. However, it does not explain the return format or the effect of the 'url' parameter on which RPC endpoint is queried, so minor gaps remain.

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 description coverage is 100% because the only parameter ('url') has a clear description of its default behavior. The tool description adds no additional parameter semantics, but since the schema already covers it, a baseline score of 3 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 identifies the tool as returning current epoch, slot index/slots-in-epoch, absolute slot, and block height. Although it lacks an explicit verb like 'get' or 'retrieve', the content effectively distinguishes it from sibling tools such as rpc_health or next_leaders by its focus on timing/block data.

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 about when to use this tool versus alternatives. The description does not mention any specific conditions, prerequisites, or exclusions, leaving the agent to infer usage solely from the output fields.

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

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

With no annotations, the description carries the burden of disclosure. It adds useful behavioral context, such as 'network-inclusive - not a landing/first-seen proxy', which clarifies the measurement semantics. It does not mention auth or side effects, but these are less critical for a read-only latency 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 one concise sentence that front-loads the main action and includes a clarifying caveat. Every word earns its place, with no 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?

Given the tool's simplicity (2 optional params, no output schema), the description covers the core purpose, default behavior, and a key behavioral nuance. It does not explain the return format, but for a latency comparison tool this is not a major gap.

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 schema has 0% coverage for parameters, and the description only implicitly references the 'urls' parameter via 'endpoints' and default vs. public. The 'samples' parameter is not explained at all, leaving its purpose unclear.

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 measures getSlot read-latency (p50) across endpoints, which is a specific verb+resource. It also distinguishes itself from siblings by focusing on latency comparison, not health or transaction submission.

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 provides clear context by mentioning the default comparison between the configured endpoint and public mainnet-beta, and the network-inclusive behavior. It does not explicitly exclude alternatives, but the use case is evident.

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

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

With no annotations, the description carries the full burden. It implies a read-only query by describing the return data, but it doesn't explicitly state that it makes an RPC call, its dependencies, or any potential errors. The 'from the current slot' phrase adds useful context about the data source.

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 that efficiently states the tool's purpose and use case, with no redundant words.

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 description is sufficient for a simple read-only tool: it states what is returned (slot leaders), the reference point (current slot), and the intended use case. It doesn't describe return format or error behavior, but the absence of an output schema and the simplicity of the tool make this acceptable.

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 mention any parameters. The schema covers url (with a description) but lacks a description for count, relying only on constraints. Since the description adds no parameter-level information, it does not compensate for the 50% schema coverage gap.

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 returns the next N slot leaders (validator identities) from the current slot, distinguishing it from sibling tools like rpc_health or priority_fee_estimate. However, it lacks an explicit verb like 'get' or 'fetch', making it slightly less direct.

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 provides a clear use case ('for timing transaction submission'), indicating when to use the tool. It does not explicitly mention alternatives or exclusion criteria, but the context is strong enough to guide selection among the sibling tools.

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

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

No annotations are provided, so the description must carry the burden of disclosing behavior. It indicates the tool reads recent fee distribution data, which is non-destructive, but it does not explicitly state it is read-only or mention rate limits or other side effects. The provided detail about the response format adds some value beyond the name.

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, well-structured sentence that front-loads the key information: what it returns, the specific percentiles, units, and the intended use. Every word earns its place, with no redundant phrasing.

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 tool with one optional parameter and no output schema, the description fully explains the output distribution and its purpose. It is complete for a fee-estimation tool and does not leave significant gaps for an agent to misuse it.

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 schema already documents the single optional 'url' parameter with 100% coverage. The description does not add additional meaning about the parameter beyond its purpose, but the schema is sufficient. The baseline of 3 applies because schema coverage is high.

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 returns a prioritization-fee distribution with specific percentiles (p50/p75/p90/max) and units (micro-lamports per CU). It also states its purpose ('to price compute-unit fees for landing'), making it distinct from sibling tools like rpc_health or submit_transaction.

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 is used for pricing compute-unit fees before landing transactions. It does not explicitly name alternatives or exclusions, but the context is clear and no sibling tool serves a similar purpose, so no exclusions are necessary.

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

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

There are no annotations, so the description must convey behavior. It mentions that latency is 'measured', implying a network call, but does not disclose side effects, error behavior, or that it performs a live request. It also does not state that the operation is read-only.

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, information-dense sentence with no filler. All listed items (health, version, slot, latency) are relevant 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?

While the tool is simple (one optional parameter, no output schema), the description only lists return values without explaining the output format or any defaults (though defaults are in the schema). It is adequate but leaves room for details like JSON structure or error conditions.

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 schema fully describes the 'url' parameter with its default behavior (SOLANA_RPC_URL or public mainnet-beta), providing 100% coverage. The description adds no additional parameter details, so the baseline of 3 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 lists the specific outputs: health, solana-core version, current slot, and getSlot latency, for a Solana RPC endpoint. This distinguishes it from siblings like priority_fee_estimate or submit_transaction, which target different operations.

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 explicit guidance is given about when to use this tool versus alternatives such as latency_compare or epoch_info. The intended use case is implied by the name and description, but no context or exclusions are provided.

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

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

No annotations are present, so the description carries the burden of behavioral disclosure. It transparently states the server never signs or holds keys and that it confirms on-chain inclusion (landed slot + time). However, it does not mention timeout/error behavior or irreversible effects.

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 short sentences with no filler; all content is functional 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?

Description covers main purpose and key behavior, and hints at output (landed slot + time). But it omits semantics/edge behavior for maxWaitMs and error handling, and with no output schema, return details are sparse.

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?

Description clarifies that the signedTransaction is 'caller-SIGNED' and 'keyless', adding meaning beyond the schema's 'fully signed transaction'. The url and maxWaitMs parameters are not elaborated beyond schema/defaults.

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?

Description uses specific verb 'Relay' and resource 'caller-SIGNED base64 transaction', with clear goal 'confirm actual on-chain inclusion'. Clearly differentiates from read-only sibling tools like rpc_health and epoch_info.

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?

It states 'sign upstream, submit here' and 'Keyless', indicating this tool is for already-signed transactions. Provides clear context for when to use, though it doesn't explicitly exclude alternatives or name sibling alternatives.

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