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

Annotations already declare readOnlyHint=false, openWorldHint=true and destructiveHint=false, so the write and public-reach profile is covered. The description adds real context beyond that: the submission goes to the Trainer Connect team and becomes public only after a review step, which tells the agent about moderation delay and public visibility.

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?

A single front-loaded sentence with no filler; the post-submission consequence is packed into one clause. It is efficient rather than padded, though the very short length leaves room unused.

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 three-parameter submission tool with annotations covering the safety profile, a documented schema and no output schema, the description supplies the one thing structured data cannot: what happens to the idea after it is sent. Nothing an agent needs to call it correctly 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 coverage is 67% with title and description length bounds documented and the category enum enumerated, so the schema carries most parameter meaning. The description adds no guidance on category choice (e.g. that 'outro' is a catch-all) or on how title vs description should differ, so the baseline 3 applies.

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?

Names a specific action (sending an idea) and a specific destination (the Trainer Connect team), which separates it from vote_feature_request, list_feature_requests and comment_feature_request in the sibling set. It stops short of naming those siblings explicitly, so an agent must infer the boundary from the phrasing.

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?

Usage is only implied: the sentence conveys that this is the entry point for new suggestions and that voting comes later. There is no explicit when-to-use, when-not-to-use, or pointer to the read/vote/comment siblings that operate on existing requests.

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