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

With no annotations, the description carries the full behavioral burden and does not say whether this is a read-only lookup, whether it takes any inputs (it does not), or whether the tiers are static protocol constants versus dynamic values. It also gives no hint of the shape of the result.

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 short and front-loads the resource, but it is a fragment rather than a sentence, and its brevity comes partly from under-specification rather than efficiency. A verb and one clarifying clause would cost little and add much.

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?

There is no output schema and no annotations, so the description is the only source of information about results, and it says nothing about what a 'tier' or 'boost multiplier' looks like. For a lookup tool whose entire value is the returned tier/multiplier data, this leaves a real 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 tool takes zero parameters, so there is no parameter semantics to explain; the baseline for a no-param tool is 4. No conflicting or undocumented inputs exist.

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 names a recognizable resource ('lock duration tiers' and 'boost multipliers' for SDL staking), which is more than a pure restatement of the name. However, it is a bare noun phrase with no verb, so it never actually states that the tool retrieves or returns these tiers. It also does nothing to distinguish it from siblings such as sdl_get_sdl_tier_distribution.

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?

There is no indication of when to call this tool, what question it answers, or which sibling to use instead (e.g. sdl_get_sdl_tier_distribution or sdl_get_competitive_staking). The agent must infer the use case entirely from the resource name.

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