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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds useful context by stating the scope is one archive folder and that the results contain id and name, but it does not discuss pagination, permissions, or response behavior beyond those fields.

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 very short, but it is a fragment rather than a front-loaded action statement, and the trailing internal reference 'Archive.DocumentFolderTabs' does not add useful guidance for an agent. It is concise but under-specified for a tool definition.

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?

The tool is a simple read-only list operation with full schema coverage and annotations, and the description does mention the returned fields (id, name). However, it lacks usage context and any guidance about relationship to the parent folder-listing tool, leaving an agent to infer how this fits into the workflow.

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%, and both parameters are documented in the schema, including where folder_id comes from. The description does not add meaning beyond the schema, which is expected when the schema already does the heavy lifting.

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 clearly identifies the resource (tabs inside one archive folder) and states the key return fields (id, name), so an agent can infer it is a listing operation. It does not explicitly differentiate itself from nearby siblings such as yuki_list_document_folders, but the per-folder scope is clear.

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 explicit guidance on when to use this tool versus alternatives, nor any stated prerequisites. The only implicit requirement is that it operates on an existing folder, but the description does not tell the agent when this is the right choice over other list tools.

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