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

Annotations already cover the safety profile (readOnlyHint, destructiveHint=false, openWorldHint), so the bar is lower. The description still adds real value by disclosing the shape of the return payload (which fields come back) in the absence of an output schema, plus the underlying GET admin endpoint — non-trivial context beyond the annotations. It does not mention pagination mechanics or rate limits.

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 tight sentences: purpose and payload first, filters second, endpoint last. Almost no waste; the endpoint mention is the only arguably redundant element and it is short.

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 16-param read tool with no output schema, the description supplies exactly the missing piece — the returned field set — while the schema carries all parameter semantics and annotations carry the safety profile. An agent has enough to select and invoke it correctly.

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?

With 16 parameters at 100% schema description coverage, the schema already documents paging, sort syntax, cursor preference, and every filter. The description only restates the filter categories generically and adds no format or constraint detail beyond the schema (e.g., nothing about cursor vs page interaction or sort syntax). Baseline 3 applies when schema does the heavy lifting.

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?

States a specific verb (list or search) and resource (suggestions/ideas), and enumerates the returned fields (title, body, state, vote/supporter counts, revenue, links). This distinguishes it implicitly from get_suggestion (single record) and create_suggestion (write), though it never names a sibling explicitly.

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 filter enumeration (text, forum, category, status, state, label, time) implies how the tool is meant to be driven, but there is no explicit when-to-use versus get_suggestion/uservoice_list_feedback_records, and no stated exclusions or prerequisites. Usage is inferable rather than stated.

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