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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuine behavioral detail beyond that: results are sorted most-voted-first and the default scope is limited to ideas still open for votes, which tells the agent what it will and won't see.

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?

One sentence with the resource and ranking stated first, then the filter exception. No filler, though the semicolon-joined filter clause is slightly dense.

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 read-only, single-optional-parameter list tool with no output schema, the description covers scope, ordering and filtering, which is what an agent needs to call it correctly. It omits result limits or pagination behavior, a minor gap for a list endpoint.

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?

The single parameter has 0% schema description coverage, so the description must compensate, and it does: mine=true is defined as returning only the trainer's own ideas. It doesn't state the default (mine=false) explicitly, but the contrast is clear enough.

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 names the resource concretely (Trainer Connect feature ideas open for votes) and the ordering, so an agent can distinguish it from get_feature_request, suggest_feature and vote_feature_request. The list verb itself is only implied by the tool name rather than stated, which keeps it short of a 5.

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 signals the use case (browsing ideas that are open for votes) and explains that mine=true narrows to the trainer's own ideas, which is useful routing context. It never explicitly names an alternative or says when not to use it (e.g. get_feature_request for a single request's detail), leaving that inference to the agent.

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