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

No annotations are provided, so the description carries the full burden. It describes the returned content categories but says nothing about freshness, pagination behavior, auth requirements, or whether the board is a fixed snapshot versus a queryable collection — meaningful gaps for a zero-annotation tool.

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?

Two tight sentences with the content list front-loaded and no filler. It is appropriately sized, though the second sentence about the website is of marginal utility to an agent.

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 read-only overview with no output schema, no annotations, and one undocumented parameter, the description explains the return content reasonably but omits usage routing and the limit semantics, leaving the agent with avoidable ambiguity.

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 single 'limit' parameter has 0% schema description coverage and is never mentioned in the description. With low coverage the description is expected to compensate, and it does not explain what is being limited or how it interacts with the 'top stories' list.

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 the resource (the crypto news board) and enumerates its contents: mood, counts, top stories by market impact, and AI digest. This distinguishes it as a composite/overview view, though it overlaps with the sibling mcw-get-digest by explicitly including 'the AI digest' without explaining the relationship.

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 when-to-use guidance at all. It never says to prefer this overview over mcw-get-digest, mcw-list-stories, or mcw-list-topics, despite the digest overlap being an obvious source of confusion for an agent choosing a tool.

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