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

With no annotations, the description carries the full behavioral burden. It does disclose ordering (newest first), the default filter (open), and a real permission trait ('every project the key allows'), which is meaningful. It stops short of anything about pagination/truncation, rate limits, or what a returned report contains.

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, no filler, with the ordering and default scope front-loaded so the agent gets the essential framing immediately.

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 3-param list tool with no annotations and no output schema, the description covers defaults and ordering but says nothing about the shape of a returned feedback report or how many items to expect. Adequate but leaves the agent guessing about the response.

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%, so the schema already documents limit, status, and project with their defaults. The description restates the status default ('open') and project scoping, adding no syntax or format detail beyond the structured fields. Baseline 3 applies.

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 ('feedback reports'), specifies ordering ('newest first'), and states the default result set ('the open ones across every project the key allows'). That is enough to separate it from get_issue (single item) and list_projects, though it never names those siblings 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?

Default behavior is clearly stated, which implies the common case (list open issues everywhere), but there is no explicit when-to-use guidance, no statement of when to reach for get_issue instead, and no mention of how to widen or narrow scope beyond the schema's own status/project fields.

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