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

Annotations already declare readOnlyHint=false, idempotentHint=false, and destructiveHint=false, so the write/non-destructive profile is covered. The description adds context annotations do not: the effect on future ranking and the condition 'Counts fully when your user is signed in', which flags an auth dependency. It does not clarify whether duplicate reports double-count despite idempotentHint=false, so it falls short of a 5.

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?

Three short sentences, no waste, with the trigger condition front-loaded before the rationale and the auth caveat. The final clause 'Counts fully when your user is signed in' is compact but slightly ambiguous about partial credit.

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 and two undocumented required parameters, the description carries extra burden it only partly meets: it explains purpose, timing, and the sign-in condition, but leaves the identity of 'name' and the token's fallback semantics to the schema. Adequate but with a visible gap for a four-parameter submission tool.

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 only 50%: 'note' and 'token' are described, but 'name' and 'worked' are not. The description implies 'worked' ('say whether it worked') and hints that 'name' is the server discovered via find_tools, but it never specifies the exact identifier (server name vs. tool name vs. URL), so it only partially compensates.

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 states a concrete action (report whether a server worked) and ties it to a distinct workflow step after find_tools, which sets it apart from all siblings. Minor ambiguity: the tool is named report_tool_outcome but the text says 'server', leaving it slightly unclear whether the thing being rated is a server or a tool.

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 a clear triggering condition ('After using a server found with find_tools') and explains the payoff ('improves the ranking for the next agent'), which tells the agent why and when to call it. There is no explicit when-not-to-use guidance (e.g., skip if the call was never made), but for a unique feedback action the context is sufficient.

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