media_pool_get_current_folder

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

The annotation readOnlyHint=true already conveys the read-only nature, so the description doesn't need to repeat that. It adds context by specifying the exact scope ('currently selected Media Pool folder'), but it does not disclose additional behavioral details such as return format error conditions or edge cases. This is consistent with the annotations, so no 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 a single concise sentence that front-loads the verb and resource. Every word is necessary and there is no redundancy or fluff.

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 tool with no parameters and a clear output schema, the description is fully complete. It leaves no ambiguity about what the tool does or what it returns, and given the trivial nature of the operation, no additional context is needed.

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 the input schema is empty. The description adds no parameter-specific semantics, but with 0 parameters, the baseline is 4 per instructions. The description contributes by clarifying what the output refers to (the current folder's name).

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 states the tool's function with a specific verb ('Get') and resource ('the name of the currently selected Media Pool folder'). It distinguishes from siblings like media_pool_get_root_folder and media_pool_set_current_folder by specifying 'currently selected'.

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 (when you need the current folder name) but provides no explicit guidance on when to use this tool versus alternatives. It lacks exclusions or alternative tool references, which is a clear gap for the usage guidelines dimension.

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