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

Annotations already declare readOnlyHint=true and idempotentHint=true, so no contradiction exists. The description adds useful scoping context, such as 'current' and 'bounded', but does not disclose other behavioral details like pagination, output format, or access requirements.

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?

The description is a single front-loaded sentence with no filler, no repetition of the tool name, and no redundant restatement of the annotations. Every word contributes to defining the resource and scope.

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 input parameters, read-only annotations, and no output schema, the description gives enough context to understand the returned content: quests and a participation path. The only minor gap is that 'scoped participation path' is somewhat vague and could leave an agent unsure about the exact shape of the output.

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?

The tool has zero parameters and 100% schema coverage, so the description has no responsibility to explain parameter behavior. The 0-parameter baseline of 4 applies, and the description correctly focuses on the data context instead.

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 identifies a specific verb ('List'), a concrete resource ('Research Commons quests'), and a scoping qualifier ('current bounded'). This makes the tool's purpose immediately distinguishable from sibling list tools like list_public_threads and list_realms.

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 phrase 'current bounded' implies this tool is for listing currently open quests, but there is no explicit guidance about when to prefer it over alternatives such as get_research_findings or get_discovery_manifest. The usage context is implied rather than stated.

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