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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is fully covered structurally. The description adds only the output shape ('compact Markdown list'), which is genuinely useful given there is no output schema, but says nothing about result caps, ordering stability, or what an empty result looks like.

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 what is returned and immediately followed by the format. Nothing is padded or redundant.

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 an 11-parameter, zero-required filtering tool with no output schema, the description covers only the output type in the vaguest terms. It omits pagination behaviour, default result limits, and how filters combine, which an agent would need to call this correctly at scale.

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 11 optional parameters documented including defaults (activity, open) and the 'me' shorthand, so the schema carries the load. The description adds no meaning beyond it, which is the expected baseline here.

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 types (issues, tasks, discussions, proposals) and the return format (a compact Markdown list), so the agent knows roughly what it gets. But the verb 'Find' is ambiguous between listing and searching, and a sibling named 'search' exists, so an agent cannot cleanly tell the two apart from this text.

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?

There is no when-to-use guidance, no mention of when to prefer this over search, read_thread, or work_queue, and no noted prerequisites. The agent must infer from parameters alone that this is a filtered enumeration tool.

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