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

Annotations already cover the read-only safety profile, and the description adds useful behavioral facts beyond them: no USDC is spent and no wallet is read. It still says nothing about what the tool returns or whether it can block, but the cost and side-effect profile is well disclosed.

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 core sentence is short and front-loaded with the key fact: this is a free health check that does not spend USDC. The trailing bracketed string ('[falcon.sol solana-wallet-intel. Free, no payment.]') is low-value noise that slightly dilutes it.

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 zero-parameter, annotation-covered liveness tool, the description covers purpose, cost, and side effects. It omits what a successful or failed response looks like, but with no output schema that is a minor 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 the 4 baseline applies. The description correctly implies no inputs are needed.

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 states a specific purpose: a free health check that confirms the MCP server is up. It also distinguishes itself from the wallet-oriented siblings by stating it does not read a wallet and does not spend USDC, so an agent can tell it apart from wallet_profile or wallet_quick.

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 gives clear context for when to use it (a free server liveness check, with no cost and no wallet read). However, it never explicitly names alternatives or states when not to call this tool, so the guidance stays implicit.

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