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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so safety is covered. The description adds the return contents (name, open/private state, suggestion counts) and the GET endpoint, but discloses nothing about pagination behavior beyond what the schema shows.

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 compact sentences with the resource and returned fields front-loaded and no wasted prose. The trailing 'Use a forum id...' clause is mildly extraneous given no such parameter exists here.

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?

With no output schema, the description partially compensates by naming the returned fields, and the schema carries pagination. However, a bare list tool with no stated ordering default or result-size behavior leaves the agent relying entirely on structured fields.

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% with all five filter/pagination params fully documented, so the baseline is 3. The description adds only a passing mention of a 'forum id', which is not actually a parameter of this tool and risks confusing the agent.

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+resource ('List the feedback forums (idea portals)') and even enumerates the returned fields. It is distinguishable from list_categories/list_suggestions by the 'forums' resource, though it does not explicitly contrast itself with those siblings.

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 only guidance is 'Use a forum id to filter or create suggestions,' which describes downstream use of the returned ids rather than when to call this tool versus the many other list_* siblings. No prerequisites, exclusions, or alternative-routing is given.

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