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

With no annotations, the description carries the full burden and does well: it discloses that the tool is paid ($0.01 USDC on Base, eip155:8453), where the x402 payment goes (params._meta['x402/payment']), and the underlying HTTP endpoint. It also signals the output is deterministic/mechanical and non-advice. It stops short of error/payment-failure behavior or rate limits.

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?

Front-loaded with purpose and returned factors, then payment and transport details in a compact block. Every sentence is functional; the endpoint URL and CAIP-2 chain id are slightly technical for an MCP caller but are legitimate payment metadata.

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 paid, single-purpose scoring tool with no annotations and no output schema, the description covers what is scored, which facts are returned, cost, and payment mechanics. The main residual gap is the undocumented required input and the absence of any note on failure/payment-refusal handling.

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% description coverage for the single 'mint' property and marks no required parameters, so an agent has no structured signal that a mint address must be supplied. The description only hints at 'one Solana token', giving no address format (base58), no note that mint is effectively required, and no clarification of what happens if it is omitted.

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?

States a specific verb+resource+scope: a mechanical 0-100 risk score for exactly one Solana token, and enumerates the factors (mint/freeze authority, holder concentration). That is clearly distinguishable from generic siblings like solcheck__token or solcheck__holders, though it never names them explicitly to route the agent.

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?

Use is implied by 'risk score' and the 'Facts only, not advice' framing, but there is no explicit when-to-use guidance and no mention of when to prefer solcheck__token, solcheck__holders, basedue__tokenrisk, or check_sanctions__token instead. The payment requirement is stated but not framed as a decision factor (e.g. use free siblings first).

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