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

The description asserts "Read-only, changes nothing," while annotations declare readOnlyHint=false, which in MCP terms means the tool may modify its environment. That is a direct conflict on the single most safety-relevant property an agent uses to decide whether to call a tool unsupervised. The pricing note "(3 MESH/call)" is genuinely useful context, but it does not offset a contradiction about mutation semantics.

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?

A single sprawling em-dash sentence that opens by restating the title verbatim, then uses "live" twice in conflicting senses ("featured items live" vs. "live or archived"). The parenthetical price/ops tag trails a sentence that is already hard to parse, so nothing is front-loaded for a scanning 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?

No output schema exists, so the description should convey what a check returns, and it gestures at this (what each item does, what a visitor can run) without committing to a structure or verdict format. Combined with the unexplained required "input" payload and the unresolved "any place" target, an agent still cannot assemble a valid, confident call from this definition alone.

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?

There is one required nested "input" object, and its schema description is generic boilerplate ("Capability-specific payload, e.g. agent-brain...") that gives no clue what this tool specifically expects. The description adds nothing about the payload shape, the target place identifier, or whether it takes a repo/org/URL. The 100% coverage figure is nominal rather than substantive.

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 does name a concrete verb and resource set ("Checks any place's featured items... pinned repos, starred projects, featured list, or highlights"), so the general intent is recoverable. But "any place" never resolves into what a place is (a repo? an org? a profile?), and the phrase "what each does, and what a visitor can run from it" mixes inspection of content with an audit of runnable entry points. It also fails to distinguish itself from plausible siblings such as readme-check, org-profile-check, or listing-upgrade-checker.

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 explicit when-to-use or when-not-to-use guidance, and no alternative tool is named. The clause "with a walk-around to the equivalent if absent" hints at a fallback behavior but is too opaque to act on as selection guidance. An agent cannot tell from this text whether to call it before or instead of readme-check.

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