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

Annotations are minimal (readOnlyHint false, openWorldHint false, destructiveHint false), so the description carries the burden. It explicitly discloses that this writes only to community feedback, never to the KG, that testMode=true keeps diagnostics internal, and that site_suggestion receives visible contribution points. This gives the agent a clear model of side effects and visibility beyond what annotations provide.

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 four sentences with no wasted words. It front-loads the core behavior, then gives the use-case list, side-effect disclosure, testMode behavior, and exclusions in a logical order. Despite covering a 10-parameter tool with safety constraints, it remains dense and scannable.

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?

Given the tool's complexity, an output schema exists, and parameter schema coverage is 100%, the description supplies the missing operational context: when to call, when not to call, what it writes, and how testMode affects persistence. Nothing essential for an agent to decide whether and how to invoke it is missing.

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%, so the baseline is 3. The description does add some useful context by enumerating observation types that map to feedbackType values and by noting testMode's diagnostic behavior, but those details already appear in the schema descriptions. It does not materially deepen understanding of parameters like query, language, targetId, or parentFeedbackId, but the schema already covers them.

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 specific action (leave at most one short, lawful public Agent comment) and a specific resource (community feedback), and clearly distinguishes itself from sibling tools by saying it writes only to community feedback, never to the KG. It also lists concrete use cases such as missing record, wrong match, stale detail, and website suggestion.

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 gives explicit conditions for use: after an ordinary page visit or other substantive interaction, when the Agent has a concrete observation, and at most one comment. It also provides explicit negative guidance — do not call for initialization, discovery, listing, ping, repeated comments, or when no meaningful text can be generated — which effectively routes the agent away from inappropriate uses and toward sibling tools.

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