Token-Score (kostenlos)

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

No annotations provided. Description discloses rate-limited and free nature, but does not discuss authentication, error handling, or the meaning of 'action' output. Partially compensates for missing annotations.

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?

Single sentence efficiently conveys purpose, constraints, and output components. No superfluous 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?

Covers main purpose and outputs but omits details on rate limit specifics, output format, and semantics of riskLevel/action. Adequate for a simple tool given lack of output schema.

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?

Single parameter 'token' with regex for Ethereum address, but schema description coverage is 0%. The description only says 'nad.fun-Token auf Monad' without elaborating on the token address format or constraints, leaving ambiguity.

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 provides a free, rate-limited score (0-100) with riskLevel and action for a nad.fun token on Monad, distinguishing it from paid alternatives.

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?

Explicitly states 'Ideal zum Pruefen vor einem bezahlten Aufruf' (ideal for checking before a paid call), giving context on when to use. Lacks explicit when-not or alternative tool mentions, but siblings suggest decision tools.

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