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

With no annotations provided, the description carries the behavioral disclosure burden. It discloses the nature of the operation ('Deep quality evaluation') and the return content ('score, signal breakdown, and specific red flags'). It does not mention network access, failure modes, or explicitly confirm read-only behavior, but for a safe-looking evaluation tool this is reasonably transparent.

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?

The description is two focused sentences with no filler. The core purpose and outputs are front-loaded, and the usage instruction ('Use this BEFORE...') earns its place. Every sentence adds value.

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-parameter tool with no output schema, the description is complete: it explains what the tool does, what it returns at a high level, and when to use it. The schema covers parameter format, and the description covers intent and expected result.

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%, with the only parameter 'tool' fully documented as a GitHub URL, owner/repo string, or tool slug. The description adds no additional parameter meaning beyond the schema, so the baseline score of 3 is appropriate.

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 names a specific verb ('evaluate'), a clear resource ('a tool or MCP server'), and distinctive outputs ('score, signal breakdown, and specific red flags'). It also lists concrete red flags like abandoned, no license, and single contributor, which separates it from sibling tools search, lookup, and recommend.

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?

The description explicitly states when to use the tool: 'BEFORE recommending or installing any tool to verify it is safe and well-maintained.' It gives clear context but does not explicitly name sibling alternatives or state when not to use it, so it falls just short of a 5.

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