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

With no annotations provided, the description carries the full disclosure burden, yet it says nothing about ordering, pagination, whether nested folders or empty results are possible, or the permission scope required. 'List' implies a read-only operation, but that is an inference the agent has to make.

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?

One short, front-loaded sentence with no filler or redundancy. It is efficient, though its brevity contributes to the gaps in behavior and return-value disclosure rather than being a virtue in itself.

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?

There is no output schema, so the description should convey the shape of what comes back, such as what fields a folder has or whether counts are included, and it does not. For a zero-parameter read tool this is a modest but real gap, since the agent cannot anticipate 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?

The tool takes zero parameters and the schema confirms an empty properties object, so there is nothing parameter-wise to document. The baseline of 4 applies; the description neither helps nor hurts 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 pairs the specific verb 'List' with the resource 'the user's research folders', making the operation unambiguous. It does not distinguish itself from siblings such as search_research or get_recent_research, so an agent must infer that this is the unfiltered enumeration rather than a search.

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 statement of when to use this tool versus get_folder_research, search_research, or get_recent_research, and no prerequisites or exclusions. The 'all' wording hints at unfiltered enumeration, but the agent must derive the routing decision from the name alone.

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