Retrieves the list of profile folders available in the specified workspace.

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds useful default behavior (first page, default order) but says nothing about permission requirements, maximum result bounds, or response shape.

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?

Three short sentences, front-loaded with the core action and followed by the optional behaviors and default. Slightly redundant with the title but free of filler.

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 read-only listing tool with no output schema and fully documented parameters, the description gives an agent enough to invoke it correctly, including the default paging behavior. It could mention permissions or result caps but is otherwise complete.

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%, so every one of the 7 parameters (id, name, start, total, sorting, location, workspaceId) is documented in the schema with defaults and format guidance. The description adds no parameter details beyond noting that filtering, sorting, and limiting exist, so baseline 3 applies.

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 states a specific verb and resource ('retrieves a list of folders available in the specified workspace'), and the name/title scope it to profile folders. It does not explicitly distinguish itself from the similar sibling get_proxy_folders, but the resource is otherwise 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?

It describes that the filters, sorting, and result limiting are optional and what happens by default ('returns the first page of profile folders in the default order'). However, it never says when to prefer this over get_profiles or get_proxy_folders, so usage is only implied.

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