Get an MCP server review

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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered. The description adds genuinely useful context beyond that: it discloses what the response contains (verdict, evaluation date, section list, content) and hints at the 'long review' size problem that motivates the `section` filter. It does not cover error behavior or rate limits, but that gap is minor.

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: the first establishes what the tool returns, the second handles the narrowing parameter. The most important information (what you get back) is front-loaded and no sentence is filler.

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?

With no output schema, the description carries the burden of describing returns, and it does so adequately by listing the four payload components. Combined with 100% schema coverage on inputs and annotations covering the safety profile, an agent has nearly everything needed; only error/edge behavior is unaddressed.

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 coverage is 100%, so the baseline would be 3, but the description contributes beyond the schema by giving concrete section examples ('setup', 'security', 'token cost', 'FAQ') that clarify the matching semantics of the otherwise abstract 'heading contains this text'. It adds nothing for `max_chars` or `server` beyond the schema.

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 and resource ('Get MCP Verdict's review of one MCP server') and enumerates the payload (verdict, evaluation date, section list, content). It is clearly distinguishable from search_servers (plural discovery) and get_guide (different resource), though it never names those siblings explicitly.

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?

It gives actionable guidance on the `section` parameter — use it to pull just one part of a long review — which implies the when-to-narrow case. However, it never states when to prefer this over search_servers or get_guide, nor any prerequisites or failure conditions, so routing is left to inference.

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