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

With no annotations, the description carries the full burden; "List" implies a read-only operation but that is inference rather than disclosure. It adds the default sort (votes), yet says nothing about pagination totals, return shape (no output schema), or whether status filtering interacts with sorting.

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 short sentences, front-loaded with the resource and its default ordering, then the use case. No filler or restated metadata.

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?

Covers what the tool returns at a high level and its default sort, which is adequate for a simple read tool with full schema coverage. However, with no annotations and no output schema, an agent still lacks any statement about response contents (e.g., whether vote counts and statuses are included) or result-set size behavior.

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 100%, so all four parameters are already documented, establishing the baseline of 3. The description adds one useful detail the schema omits — that sorting defaults to votes — but does not clarify offset/limit interaction or status semantics.

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 and resource ("List the project's feedback items") plus the default ordering, so the agent knows exactly what it retrieves. It does not distinguish itself from siblings such as search_feedback or feedback_summary, so it stops 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?

"Use this to see what users are asking for most" gives an implied usage scenario tied to vote sorting. There is no explicit when-not guidance and no mention of when to prefer search_feedback or feedback_summary instead.

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