list_folder

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

Annotations already declare readOnlyHint=true, so the read-only nature is known. The description adds useful behavioral context by stating the ordering of contents (skills first, then files) and that skills are 'by reference'. This exceeds the baseline provided by annotations without contradiction.

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 two sentences plus a brief Args section. It is front-loaded with the core purpose and includes no unnecessary words. Every element serves a clear communicative function.

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 simple read-only tool with one required parameter and no output schema, the description covers the essential aspects: what is listed, the order, and where to obtain the folder_id. The config parameter is a minor omission, but the tool is otherwise adequately described given its simplicity.

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 0%, so the description must compensate. It explains folder_id with a source hint ('from list_folders or create_folder'), which adds meaning beyond the schema. However, the optional 'config' parameter is completely undocumented, leaving a gap in parameter understanding.

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 uses a specific verb ('List') with a clear resource ('a folder's contents') and specifies the ordering and composition (skills by reference first, then files). This clearly distinguishes it from sibling tools like list_folders and list_skills, which have different scopes.

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 description implies usage by indicating the folder_id comes from list_folders or create_folder, but it does not explicitly state when to use this tool versus alternatives or provide exclusions. The context is clear but not fully elaborated.

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