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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the write/safe nature is partly covered. The description adds real value beyond that by stating the feedback is private, goes to editorial review, and 'never publishes content' — a meaningful disclosure about side effects. It omits auth requirements and rate/duplicate-submission behavior.

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 sentences, front-loaded with the action and immediately followed by the key constraint and the non-publication guarantee. Nothing is padded or repeated from the title.

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?

An output schema exists, so return values need not be explained. But for a 7-parameter tool with 0% schema coverage, the description addresses only the target selection and the non-publishing behavior, leaving the category enum, optional metadata fields, and idempotency field entirely unexplained.

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 0% across 7 parameters, so the description carries the full explanatory burden. It only clarifies the article_id/topic_id target ('one published article or topic') and says nothing about category, text, source_url, display_name, or client_submission_id, leaving most parameters undocumented.

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 verb and resource ('Submit private feedback for editorial review') and clarifies the destination (editorial review), which separates it from publishing-oriented siblings like publish_study_path and propose_project. It stops short of naming any sibling explicitly, so it is clear but not maximally differentiated.

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?

'Provide one published article or topic' implies the expected context of use and constrains the target, and 'this never publishes content' rules out one misuse. However, it gives no guidance on when to choose this over siblings such as suggest_connection or propose_project, leaving selection to inference.

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