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

With no annotations, the description carries the full burden of behavioral disclosure. It only hints at informational content ('crypto info') but does not state whether the operation is read-only, what side effects exist, or what the response shape resembles. Minimal transparency is provided.

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 vague phrase. While brief, it is under-specified and does not earn its place due to lack of useful content. This is more under-specification than effective conciseness.

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 complexity is low (no params, no output schema), but the description's ambiguity about 'crypto info' creates a significant gap. It is unclear whether this refers to cryptocurrency, cryptographic primitives, or something else, making the tool incompletely described for an agent.

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 zero parameters, and the input schema is empty. Per baseline, no parameter description is needed; the score is set to 4 as there is no additional semantic burden.

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 'Server status + crypto info' is vague and lacks a clear verb. It fails to specify what the tool actually does (e.g., retrieves, checks, returns) and does not distinguish it from sibling tools like 'ping' or 'anchor_status' which also relate to status.

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 on when to use this tool versus alternatives. The description gives no context for appropriate usage or exclusions, leaving the agent without any decision support.

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