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 discloses the frequency constraint ("once per task") and the rating scale, but says nothing about auth requirements, what the rating affects, or what the response looks like.

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 short, front-loaded sentences with zero waste. The core action and the frequency instruction are both stated immediately.

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 low-complexity tool with no output schema and no annotations, the description covers the basics but omits the comment parameter and any differentiation from report_mcp_feedback. It leaves meaningful gaps for correct invocation.

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?

With 0% schema description coverage and 2 parameters, the description must compensate. It implies the stars value (1-5), matching the schema's min/max, but the optional comment parameter is entirely undocumented in both the schema and description.

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 (rate) and resource (these MCP tools) with a concrete scale (1 to 5 stars). It's clear what the tool does, but it doesn't distinguish itself from the sibling report_mcp_feedback, leaving an agent to guess which feedback channel applies.

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?

"for the task you just finished" and "Call it once per task" give clear timing and frequency context. However, it offers no exclusions or explicit comparison to report_mcp_feedback, so the boundary between the two feedback tools is unstated.

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