lazareus

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

With no annotations, the description carries the full burden. It adds useful context (the cost via x402 and the type of degradation checked) but does not explicitly state the return value format or whether it is a simple boolean. It implies a read-only check but lacks explicit detail on response structure or side 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?

The description is two sentences, front-loaded with the core function, then a use case, then cost. Every sentence adds value and there is no wasted text.

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 tool with no parameters and no output schema, the description covers the purpose, use case, and cost. It lacks an explicit statement about return values, but 'checks whether' strongly implies a boolean result. The absence of error conditions or additional context is a minor gap, but the tool is simple enough that this is nearly complete.

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 tool has 0 parameters, so the baseline for parameter semantics is 4. The description does not need to explain parameter syntax or meaning, and no compensation is required.

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's purpose: 'Checks whether the Solana network is currently going through a period of degradation' with specific indicators (congestion, slower slot production, abnormal delinquency rate, skipped slots). This is a specific verb+resource that distinguishes it from the sibling tool (is_validator_delinquent) which checks a specific validator.

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: 'Useful before executing a timing-sensitive transaction.' This tells the agent when to use it. However, it does not explicitly mention when not to use it or compare it to the sibling tool, though the network-wide vs validator-specific distinction is implied.

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 indicates a read-only nature with 'Checks whether' and discloses the cost ($0.001 per call via x402). It doesn't detail error handling or exact return format, but the name and phrasing sufficiently imply a boolean response.

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 consists of three concise sentences: purpose, use case, and cost. Each sentence adds distinct value with no redundancy or filler.

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 one-parameter lookup with no output schema, the description covers what it does, when to use it, and its cost. The only minor gap is no explicit statement of the return value, but 'is_validator_delinquent' strongly implies a boolean 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?

Schema description coverage is 100% as the single parameter 'address' is described as 'The Solana validator's vote account address'. The description adds no extra parameter details, so the baseline score of 3 applies.

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 the specific verb 'Checks' and clearly identifies the resource: a Solana validator's delinquency status. It distinguishes itself from the sibling tool 'is_network_degraded' by focusing on an individual validator rather than network-wide conditions.

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 concrete use cases: 'Useful before delegating stake or deciding whether to withdraw a delegation urgently.' It gives clear context for when to use the tool but does not explicitly mention when not to use it or directly compare with alternatives.

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