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

Annotations already cover readOnly/idempotent/non-destructive/openWorld, so the bar is lower, and the description adds genuinely new context: creator-written fields are untrusted and prompt-injection-bearing, untrusted fields are surfaced under untrusted.fields, and the server never requests keys or signatures. It does not discuss caching, freshness, or rate limits, so it stops short of a 5.

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?

It is compact and front-loads what MPAD is before the warnings. Each clause carries a distinct safety or scope point, though the run of colon-separated disclaimers (volatility, not investment advice, no keys) reads as boilerplate padding the tail.

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 single-optional-param, no-output-schema tool, the description gives the payload contents, the untrusted-field convention, and the safety posture, which is enough to call it correctly. Minor omissions are the lang parameter's effect and any pagination or caching behavior.

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?

Schema description coverage is 100% and the single optional lang enum is fully documented there. The description never mentions lang or the risk-notice language, so it adds no meaning beyond the schema; baseline 3 applies.

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 the specific resource (MPAD, the memepad operator's token) and its payload (market data plus the operator's interest disclosure). An agent can tell it is a data-retrieval tool, but nothing distinguishes it from the similar sibling get_coin, which likely returns token data too.

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 guidance on when to call this rather than get_coin, get_platform_info, or search_coins. The description only asserts 'Read-only data,' leaving selection entirely to inference from the name.

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