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

Annotations already declare read-only, idempotent, closed-world and non-destructive, so the safety profile is covered. The description adds genuinely new behavior: next_cursor is null on the last page and must be passed back as cursor with the same filters, plus what each returned idea carries (votes, voted, following, author by name only) and that counts aggregates area and q by status. It stops short of describing ordering stability or error 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?

Nearly every clause carries information, but the pagination contract is buried mid-sentence inside the opening line and the prose reads as one long run-on. Splitting the page/cursor rule into its own sentence would front-load the most operative detail without adding length.

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 seven-parameter, zero-required listing tool with no output schema, the definition covers ordering, filtering, pagination, and the shape of the returned rows and counts. The main remaining hole is the area filter, which is undocumented in both the schema and the description.

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?

At 57% schema coverage, the description compensates well: it supplies the default limit of 30 that the schema omits, defines the cursor round-trip contract, and interprets the status enum values (open expands to under_review, planned, in_progress). It adds little for area, whose enum has no description in either place, and leaves sort entirely to the schema.

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 (Community board ideas), the ordering (most voted first), the scope (Everyone's ideas for Kinetune) and the paging model, which is enough to separate it from get_idea and suggest_idea. The opening clause is awkwardly spliced ('with your vote and follow Everyone's ideas...'), which costs it a point on precision.

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 gives a concrete workflow rule: before suggesting an idea, search with q and vote for an existing one instead of duplicating. It also explains the filtering intent of status and yours. It never explicitly contrasts itself with get_idea or suggest_idea by name, so routing is implied rather than spelled out.

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